yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Android Development] JohnLocke44:
I have a doubt before I flash this ROM.

Does the camera shoots photo in 16:9?

Thanks!

Enviado de meu Nexus 7 usando Tapatalk 4
[Galaxy S 4 i9505 Android Development] impact1991:
Its 4128x3096 so 4:3.

First, thank you for this very nice Rom! :good:

I have a question, how can i enable battery power in percentage?

greetings

Edit: Made it by myself :D

Edit2: Battery Life is unfortunately a grande maleur. only 15 hours with moderate usage and 1 hour 30 min on screen time...
[Galaxy S 4 i9505 Android Development] friedrich420:
I know it's OT but since I put the energy in creating it, i figured i share it...

[INDEX][I9505] CUSTOM ROMS LIST [UP TO DATE and COMPREHENSIVE]
[Galaxy S 4 i9505 Android Development] salamt:
Thanks for sharing I am going to test it now. Any feedback on the battery drain if it is fixed in this release?
[Galaxy S 4 i9505 Android Development] friedrich420:
Even though I havent used it in a long time (sorry my friend im not supporting this thread that much anymore given my other Rom...) it was unfortunately pretty much very similar battery drain as the 1st release...
[Galaxy S 4 i9505 Android Development] donalgodon:
Can quick settings toggles be added or edited on this ROM the way they can on CM/AOSP?
[Galaxy S 4 i9505 Android Development] skaarax:
I have seen roms from i9505 installed on a 337M with no problem, do you think i can install this rom on a i337M??? :p
[Galaxy S 4 i9505 Android Development] donalgodon:
Is there an odexed version of this ROM mirrored somewhere? All I've found are dead links.
[Galaxy S 4 i9505 Android Development] astuermer:
Is HDMI out working on this ROM?
[RAZR HD Q&A, Help & Troubleshooting] kuz142:
Looking through the ROMs in the development forum, it really seems like they all require an unlocked bootloader and a different recovery than Safestrap (CWM I've seen the most).

However, I'd prefer not to have to install over the stock ROM at first, and also to keep the bootloader locked if possible since unlocking it is an irreversible process (as far as I know -- any corrections on that are welcome).

So my question is -- does anyone know of some good ROMs for the Razr HD that can be installed using the Safestrap ROM slots? Thanks
[RAZR HD Q&A, Help & Troubleshooting] bananapeapod:
I was in your same boat a few weeks ago and found out that the safestrap ROMs aren't being developed actively anymore. I took the plunge with the Razr HD utility from the original development sub section and between titanium backup and having a stock nandroid backup with data I haven't felt unsafe at all!
[RAZR HD Q&A, Help & Troubleshooting] koftheworld:
If you're still unsure about unlocking, there are a few ss roms out there that are still good.I personally prefer nexesque out of the ones still available.it's over at dr.

sent from my xt926 RAZR maxx hd
[Nexus One Q&A, Help & Troubleshooting] sachinguru:
Hi Guys, i my Google nexus one stuck on boot screen.i had read lots of post on XDA to solve this problem but not able to solve.

My Nexus one has unlocked bootloader.

I flash recovery from fastboot and it successfully flashed.

but when i try to boot into recovery mode, device stuck on boot screen with lock symbol below, which denots unlock bootloader.

Please can any buddy tell what the problem or how can it flash custome rom into it .

Thanks .
[Nexus One Q&A, Help & Troubleshooting] hxq88:
try wipe all partition again

fastboot -w
fastboot erase recovery
fastboot reboot-bootloader

and reflash recovery

must use 4ext recovery :)

Edited: fixed
[Nexus One Q&A, Help & Troubleshooting] demkantor:
Replace hboot with fastboot in the above commands
[Nexus One Q&A, Help & Troubleshooting] rickz41:
HTC Nexus One Problems- All Self-inflicted

Hi, First off, I'm so damn new I don't even qualify yet to be called "Noob". I bought an HTC Nexus One on eBay and it was loaded with 2.3.4. But I could not get it to update. I then took a look at the build # "3.11.405.2CL81940" with "release keys" added in a line below. Google came up with two or three hits, all starting with "Weird Build....", so I decided to get rid of it by rooting the phone. Over three days of fooling around with it and I am asking for help: after doing ALL KINDS OF THINGS (can't even remember the sequence), I'm stuck with a phone which when powered on no longer goes to the "X" splash screen but to "htc" with small yield signs with exclamation points in the four corners of the screen. The only way to power it down is to remove the battery. If I connect it to my Windows PC, it is recognized (I've downloaded the drivers, SDK Manager and AVD Manager) and I can perform certain functions using the command line within the SDK. But I can't format and start all over with a "stock" release let alone Jelly Bean which was my goal when starting all this. Additional information I can provide: when I remove the phone from the USB, the Black "htc" screen disappears and a white screen replaces it with the following: Line 1) BlackRose-Made by LeCache dl95244; line 2) STOCK 145/95/196; line 3) NEXUS ONE PV(or U)T S-off; line 4) HBOOT 7.3.5.5017 (PB9910000); line 4) TOUCHPANEL SYNT0103; line 5) RADIO-5.12.00.00; line 6) Apr 21 2012, 04:53:16; line 7) RUU. Line one, "BlackRose...", is black with white characters. Lines 2-6 are green characters on a white background (resembling the old boot screen) and finally, line 7, the "RUU" characters are white in an orange background, as though it's highlighted, asking for something. As said above, no buttons work (Track ball, Vol up/Vol down), and this is where the battery has to be pulled to power it down. Can anyone help?? I'll do my best to reply with any specifics that I DO remember, but I've done so many, many things in the past three days I've lost track. Thanks.
[Nexus One Q&A, Help & Troubleshooting] demkantor:
When you plus your phone into PC does it make a noise as if the phone is recognized? When you first get to the screen with the black rose text does some words flash then disappear?

And really no buttons work at all?
[Nexus One Q&A, Help & Troubleshooting] rickz41:
In response to your question:

Let me describe it from the start. After insuring the device is fully charged I power it off the only way I can, pulling the battery, waiting 5 seconds, then reassembling the battery and back.

I get out the USB cord and insert it into the Windows PC. Then, (either powered on BEFORE insertion of the Micro USB or AFTER), when the device is powered on it goes to a new splash screen with "htc" in white on a gray/black background with caution signs at each corner of the screen. The device will stay that way for hours, plugged into a PC or powered on without tethering. THE ONLY WAY to access the white screen (which resembles the old boot screen without skateboards) is to unplug the device from the USB/PC WHILE POWERED ON.

When you do this, you have the "BlackRose" in white on a black line, then the rest as described, with "RUU" in orange.

There is one additional detail I do remember doing: I downloaded and installed "HTC One (M7//T-Mobile/AT&T/Sprint) AIO Kit by Hasoon2000v2.1 and Flashed CWM (GSM Only) Recovery. That was the last time the screen was at all responsive: lot's of lines rolling upward and then the words, I think, "Update failed".

Hasoon2000, I believe, is a member of this Forum and lives in Orland Park, IL, a suburb frustratingly close to me, in Chicago!!

---------- Post added at 07:02 AM ---------- Previous post was at 06:55 AM ----------

Short answer, yes: Device Manager recognizes it and I hear a "cer-chunk" when its plugged in.
[Nexus One Q&A, Help & Troubleshooting] hxq88:
now you can enter bootloader or not?
[Nexus One Q&A, Help & Troubleshooting] rickz41:
bootloader

Yes. I can access bootloader. Just finished the following:

fastboot device HT0ALP801351

---------- Post added at 09:29 AM ---------- Previous post was at 09:09 AM ----------

OKAY [ 4.628s]

formatting 'userdata' partition...

Erase successful, but not automatically format

Can't determine partition type.

OKAY [ 0.017s]

erasing 'cache'...

OKAY [ 2.230s]

formatting 'cache' partition...

Erase successful, but not automatically format

Can't determine partition type.

OKAY [ 0.019s]

finished. total time: 6.903s

C:\android-sdk\platform-tools>fastboot erase r

erasing 'recovery'...

OKAY [ 0.097s]

finished. total time: 0.099s

C:\android-sdk\platform-tools>
[Nexus One Q&A, Help & Troubleshooting] hxq88:
its ok :D. did you run commands in post #2?

let try full wipe all and try it from beginning 1 more time. or use PASSIMG method to fast restore stock rom.

edit: ok full wiped, now reflash recovery ( try 4ext or TWRP, sorry i dont know link, you can find in search forum :D)
[Nexus One Q&A, Help & Troubleshooting] rickz41:
Post 2

Was following your guide in post 2, yes. It accepted the first two commands but the third, "fastboot reboot bootloader" caused the terminal window to only scroll my options. I don't know what you call that but I think it means it did not work.
[Nexus One Q&A, Help & Troubleshooting] hxq88:
wrong command: it must be fastboot reboot-bootloader
[Nexus One Q&A, Help & Troubleshooting] rickz41:
command

Success!!

C:\android-sdk\platform-tools>fastboot reboot-bootloader

rebooting into bootloader...

OKAY [ 0.028s]

finished. total time: 0.029s

C:\android-sdk\platform-tools>

(Phone powered off- heard PC disconnect then reconnect, now screen is still same: whit "htc", black background with caution marks, all four corners....
[Nexus One Q&A, Help & Troubleshooting] hxq88:
enter bootloader again and reflash recovery cuz all was wiped. but after wipe phone will auto-enter bootloader, i never see htc caution before.

let try reflash recovery ( 4ext or TWRP ) hope it will work.( with my phone, it somtimes stuck if i enter recovery after flash, just turn off the phone, wait 5-10 mins, idont know why :D)

edit: its the name of recovery, i miss some letter cuz fast type :P
[Nexus One Q&A, Help & Troubleshooting] rickz41:
additional info

Here I must repeat, I am not even Newbie or Noob- I am less than Noob!! What is 4ext, TWRP?? I will download them and do as you say but give detailed instructions for I am only an infant!! (when it comes to this, at least!)

---------- Post added at 10:55 AM ---------- Previous post was at 10:09 AM ----------

THANK YOU SO VERY MUCH FOR GETTING ME THIS FAR!!

It is greatly appreciated.

I will leave for awhile now, but thank you again. :D
[Nexus One Q&A, Help & Troubleshooting] demkantor:
Those are recoveries, personally 4ext tends to be the best for all phones I've used it in but for some reason I have had issues with this on my n1, the only recovery that has never given me an issue on the n1 is amonra so that's what I use, feel free to use what you like.

That screen you were stuck in earlier is RUU mode which is meant to be used flashing official HTC RUUs, I don't think you will have an serious issues, just follow directions posted earlier

fastboot erase system -w

fastboot erase boot

fastboot flash recovery recovery.img

Then scroll to recovery option in bootloader to go into whatever recovery you chose and the flash a compatible ROM at this point

If you want to learn more about fastboot see here

http://xdaforums.com/showthread.php?p=41374534
[Nexus One Q&A, Help & Troubleshooting] rickz41:
Progress thus far:

Thank you for joining in and I must say at that I am in complete agreement with your feelings re: apple/MAC/iOS, etc.: they can go to Hell.

Let me post the results after following your instructions above:

C:\android-sdk\platform-tools>fastboot erase system -w

erasing 'system'...

OKAY [ 3.406s]

erasing 'userdata'...

OKAY [ 4.608s]

formatting 'userdata' partition...

Erase successful, but not automatically formatting.

Can't determine partition type.

OKAY [ 0.023s]

erasing 'cache'...

OKAY [ 2.223s]

formatting 'cache' partition...

Erase successful, but not automatically formatting.

Can't determine partition type.

OKAY [ 0.022s]

finished. total time: 10.293s

C:\android-sdk\platform-tools>fastboot erase boot

erasing 'boot'...

OKAY [ 0.054s]

finished. total time: 0.057s

C:\android-sdk\platform-tools>fastboot flash recovery recovery-RA-passion-v2.2.1

.img

sending 'recovery' (3366 KB)...

OKAY [ 0.483s]

writing 'recovery'...

OKAY [ 1.082s]

finished. total time: 1.570s

But the n1 is still showing the gray/black splash with htc and the caution/yield signs at the corner. The line: "Erase successful, but not automatically formatting. Can't determine partition type." when erasing user data and formatting cache, is this something to be looked into?

I've flashed, I believe, successfully, AmonRa before but when I try to flash a 'Stock' passion image, it fails.

I'll continue reading your most helpful guides and hope for a step-by-step reply- I feel as though I am very close to solving this!

Again, many thanks!
[Nexus One Q&A, Help & Troubleshooting] rickz41:
Update

Sorry to report I've not made any progress since my last post despite the Guides provided.

A couple important points:

a) I cannot enter to cmd prompt level, fir whatever reason

b) This leave me with Fastboot and when the device is again wiped and prepared, Fastboot is entered, and I type Fastboot update update.zip with the following results attempting different "Stock Passion Images":

C:\android-sdk\platform-tools>

C:\android-sdk\platform-tools>fastboot update update.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: 7.35.5017

Baseband Version.....: 5.12.00.08

Serial Number........: HT0ALP801351

--------------------------------------------

checking mid...

OKAY [ 0.003s]

checking product...

OKAY [ 0.003s]

checking version-bootloader...

FAILED

Device version-bootloader is '7.35.5017'.

Update requires '0.35.2017' or '0.35.0017'.

finished. total time: 0.047s

C:\android-sdk\platform-tools>fastboot update update.zip

archive does not contain 'android-info.txt'

archive does not contain 'android-product.txt'

error: update package has no android-info.txt or android-product.txt

C:\android-sdk\platform-tools>fastboot update update.zip

archive does not contain 'android-info.txt'

archive does not contain 'android-product.txt'

error: update package has no android-info.txt or android-product.txt

C:\android-sdk\platform-tools>

C:\android-sdk\platform-tools>fastboot update update.zip

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

archive does not contain 'system.sig'

--------------------------------------------

Bootloader Version...: 7.35.5017

Baseband Version.....: 5.12.00.08

Serial Number........: HT0ALP801351

--------------------------------------------

checking mid...

OKAY [ 0.003s]

checking product...

OKAY [ 0.003s]

checking version-bootloader...

FAILED

Device version-bootloader is '7.35.5017'.

Update requires '0.35.2017' or '0.35.0017'.

finished. total time: 0.047s

Any further thoughts??

Also, USB debugging is OFF complicating thins a lot, preventing me from getting a token from HTC's site!!
[Nexus One Q&A, Help & Troubleshooting] demkantor:
Bootloader should be unlocked being you have black rose, try different RUUs

http://xdaforums.com/showthread.php?p=7495397

You may also try to change your cid to 11111111 this will allow you to flash any version
[Nexus One Q&A, Help & Troubleshooting] demkantor:
Try

fastboot oem getvar cid

To read it and

fastboot oem write cid 11111111

To write

As for which ruu to pick I'm not sure, never ran one on my n1, I did see a thread not to long ago where someone was trying to grab every official update from HTC, you can also try HTC directly and try to find the latest one
[Nexus One Q&A, Help & Troubleshooting] rickz41:
Results of cid-nahda

C:\Program Files\Android\android-sdk\platform-tools>fastboot oemgetvarcid

usage: fastboot [ <option> ] <command>

commands:

update <filename> reflash device from update.zip

flashall flash boot + recovery + system

flash <partition> [ <filename> ] write a file to a flash partition

erase <partition> erase a flash partition

format <partition> format a flash partition

getvar <variable> display a bootloader variable

boot <kernel> [ <ramdisk> ] download and boot kernel

flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it

devices list all connected devices

continue continue with autoboot

reboot reboot device normally

reboot-bootloader reboot device into bootloader

help show this help message

options:

-w erase userdata and cache (and format

if supported by partition type)

-u do not first erase partition before

formatting

-s <specific device> specify device serial number

or path to device port

-l with "devices", lists device paths

-p <product> specify product name

-c <cmdline> override kernel commandline

-i <vendor id> specify a custom USB vendor id

-b <base_addr> specify a custom kernel base address

-n <page size> specify the nand page size. default:

2048

-S <size>[K|M|G] automatically sparse files greater th

an

size. 0 to disable

C:\Program Files\Android\android-sdk\platform-tools>fastboot oem write cid 11111

111

...

(bootloader) [ERR] Command error !!!

OKAY [ 0.008s]

finished. total time: 0.009s

C:\Program Files\Android\android-sdk\platform-tools>

Found this:

http://theunlockr.com/roms/android-roms/htc-roms/htc-nexus-one-roms/

I'll start plowing through 'em- the 'original' n1 links are 404's.

By the way, Thanks a Helluva lot!!
[Nexus One Q&A, Help & Troubleshooting] demkantor:
Need the spaces

fastboot oem grtvar cid

But no worries, your bootloader isn't allowing the write so it will need to be changed to one that works or get an RUU that works

http://xdaforums.com/showthread.php?p=38435297

This is the link I was thinking of from before
[Nexus One Q&A, Help & Troubleshooting] rickz41:
fastboot oem get_identifier_token+RUU

I finally made it back (long story) and was able to get to step 8 on htc's site for the oem identifier token, failing multiple times- is this because I wiped the device??

C:\Users\Admin>cd C:\Android

C:\Android>fastboot oem get_identifier_token

...

(bootloader) [ERR] Command error !!!

OKAY [ 0.008s]

finished. total time: 0.010s

C:\Android>fastboot oem get_identifier_token.

...

(bootloader) [ERR] Command error !!!

OKAY [ 0.008s]

finished. total time: 0.010s

C:\Android>fastboot oem get_identifier_token

...

(bootloader) [ERR] Command error !!!

OKAY [ 0.008s]

finished. total time: 0.009s

So now on to your link looking for a STOCK RUU.

Ran across this:

2.2 FRF91 0.33.0012 32.36.00.28U_4.06.00.12_7 N/A FRF91 from ERE27

FRF91 from EPE54B

FRF91 from FRF85B

Full ROM

Which one??
[Nexus One Q&A, Help & Troubleshooting] demkantor:
Anyone that is a newer version than yours

You shouldn't need the HTC unlocked bootloader business, this is a nexus

fastboot oem unlock

Unlocks your bootloader, but having blackrose boot means your phone is far past this point, I was saying to check HTC for the latest ruu, its usually posted under downloads
[Nexus One Q&A, Help & Troubleshooting] rickz41:
understood

the last RUU I was messing with opening with had this (see capture attachment). It's exactly the screen on my device and the red printing below mentions the error signs....

I'll look for an RUU

Thanks
[Nexus One Q&A, Help & Troubleshooting] rickz41:
Think I'm onto something-

Sleepless night- but I DID remember the last thing I did before things went haywire: http://xdaforums.com/showthread.php?p=43869586&posted=1#post43869586 Hopefully he'll know what to do!

Thanks to all!!
[Nexus One Q&A, Help & Troubleshooting] demkantor:
Ahhh, I get it now, you flashed firmware from the HTC one onto your nexus one. Surprised it took any of it.

Hopefully you don't need JTAG, that'd kinda the last resort

Can you write down all that is currently on bootloader screen here?
[Nexus One Q&A, Help & Troubleshooting] rickz41:
Details requested

It went halfway then booted up to the black "htc" screen with the cautions in all four corners. The white, "Boot" screen ONLY, ONLY appears when the device is powered on and connected to the PC. WHEN YOU UNPLUG the device from the USB, the white screen pops up with the following:

Line 1) BlackRose-Made by LeCache dl95244; line 2) STOCK 145/95/196; line 3) NEXUS ONE PV(or U)T S-off; line 4) HBOOT 7.3.5.5017 (PB9910000); line 4) TOUCHPANEL SYNT0103; line 5) RADIO-5.12.00.00; line 6) Apr 21 2012, 04:53:16; line 7) RUU. Line one, "BlackRose...", is black with white characters. Lines 2-6 are green characters on a white background (resembling the old boot screen) and finally, line 7) the "RUU" characters are white in an orange background, as though it's highlighted, asking for something.

"JTAG" sounds serious (without researching it yet)!!

Thanks for keeping up with me!
[Nexus One Q&A, Help & Troubleshooting] demkantor:
ok so i decided to look through your posts and see if anything pops up to me

my bootloader screen look almost exact to yours

only differences is partition layout (second line no big deal though) the date and you didnt mention microp-0b15 although yours appears to be 0c15

also yours seems to be stuck in ruu mode, or at least it was when you ran the getvar all command

when i fastboot oem rebootRUU i see this

Which sounds different than your screen, i do remember seeing these triangles or at least reports of them in other phones, forget where off hand... ill try to look into it but im not sure if it will matter.

so where it stands you did some wonky things to your phone, i dont think anything caused permanent damage though.

can we get you to just fastboot mode on your phone, not ruu mode? as in when in ruu mode just

fastboot reboot-bootloader

or

fastboot oem gotofastboot

also try these

fastboot oem jump

fastboot oem boot

fastboot oem partition_test all

fastboot oem list_partition_emmc

fastboot oem get_sector_info_emmc

can you write down what output to all these commands, and if possible be in fastboot more, not ruu mode when running them

oh and yeah jtag is extreme, not something a novice should attempt and you need uart/serial communication with your phone, could cost 80$ or more just for equipment, hours of learning... but the software is free :laugh:

fastboot oem rbchk
[Nexus One Q&A, Help & Troubleshooting] rickz41:
Thanks for the time, trouble and POSITIVE suggestions! I'll do as you asked and report the results back here on this thread and forget "hassoon2000" who's too busy, it sounds, hiring lawyers... haha:

http://xdaforums.com/showthread.php?p=43869586&posted=1#post43869586

I clearly said in original post: "Please know that hold you harmless for anything I have done to my device: it is my own responsibility." Oh well- people in Minneapolis seem nicer than Orland Park.

Thanks again!
[Nexus One Q&A, Help & Troubleshooting] demkantor:
Yeah I think the issue sounds as you are stuck in ruu mode, you need to get the phone to be in fastboot mode when connected to USB, unfortunately your phone is evil and doesn't seem to want to.

So know I'm wondering if we can get it to fake boot to recovery and try changing bootloader there as all attempts to change from within bootloader has failed, try this

Open a cmd/terminal in the same folder as a recovery image, whichever one you want

fastboot boot recovery.img

(Or whatever the recovery image is named)

What happens here?
[Nexus One Q&A, Help & Troubleshooting] rickz41:
Dead-

You're right: "[This] phone is evil".

As of this time and date, let history record that this Nexus One will no power up even though fully charged.

As General Mac Arthur said on the stern of the SS Missouri at the formal surrender of the Imperial Japanese Armed Forces, "These proceedings are closed".

If you're ever in Chicago, look me up for beers- I owe you a lot. :good::good::good:

Thanks.
[Nexus One Q&A, Help & Troubleshooting] demkantor:
Haha, will do

The date I was referring to is the bootloader date, no big deal though just comparing

Did you try to force boot recovery?