Related
Note: You *MUST* be s-OFF for this to work properly. If you're not, it won't work.
1. Download this zip file: http://www.mediafire.com/?mi4utrhbacdbbxt mirror: http://www.megaupload.com/?d=LSR7QG9W
2. Rename it to PB31IMG.zip (uppercase name and lowercase extension matters, make sure it's not .zip.zip also) and push it to the root of your sdcard, so it's /sdcard/PB31IMG.zip
2 1/2. MAKE A NANDROID BACKUP (in case you ever want to go back)
3. Reboot into HBOOT by holding vol down while booting up, or by typing "adb reboot oem-42"
4. Hit vol-up when it asks if you want to apply the zip.
5. Wait for it to finish, then reboot when it asks you to.
Congrats, now you're back to stock 2.1-update1 with the original 1.00 radio.
thanks to aiccucs for his work in compiling the stock zip!
Cheers, mate.
just curious but don't you also need to put back the stock recovery back on? and that zip is stock without root, right?
the337 said:
just curious but don't you also need to put back the stock recovery back on? and that zip is stock without root, right?
Click to expand...
Click to collapse
Completely stock without root. Includes stock system, kernel, recovery, radio, and HBOOT as well as a data wipe. The only thing not stock is the fact you're still going to be S-OFF, but that's nothing really to worry about. VZW techs don't really know how to check that .
Doing this will 100% allow you to receive the OTA when Verizon finally releases it right?
ZFriedenreich said:
Doing this will 100% allow you to receive the OTA when Verizon finally releases it right?
Click to expand...
Click to collapse
Yes.
/10char
good work A++++
I had originally pulled the stock Rom image from the RUU (ran the RUU and snagged the image from the temp folder). I was able to flash back to that but had to do some trickery first pushing some files over to the phone in and then running some commands in ADB. Is this just that same image extracted directly from the stock RUU? Or has this been modified in some way?
I'm assuming it's either been modified to allow flashing without pushing those other two files first, or s-off disables the check that would normally throw a "image you are attempting to flash is older" error.
I thought we could just flash stock recovery and apply the OTA... This route, we lose all our settings and apps, correct?
Sent from my Incredible via TapaTalk...
Awesome post! Thanks man
Sent from my ADR6300 using XDA App
And having S-Off, if VZW tries to remove our root ability, all we would have to do is install SU back on correct?
Can't you just apply the ruu's with the new clockworkmod?
Sent from my ADR6300 using XDA App
I got the following quote from http://unrevoked.com/rootwiki/doku.php/public/forever
"How can I use S-OFF to recover from an unrooted update?
S-OFF gives your device permanent NAND unlock in the booted system, and also disables HBOOT's signature checking on firmware zip files. So, even if you take a OTA that has not been rooted, you can simply flash a new recovery that allows you to install su, and use that to restore yourself to a fully rooted system. We have provided ClockworkMod and Amon-Ra recovery images for you to use for this purpose. "
Hatman41 said:
I got the following quote from http://unrevoked.com/rootwiki/doku.php/public/forever
"How can I use S-OFF to recover from an unrooted update?
S-OFF gives your device permanent NAND unlock in the booted system, and also disables HBOOT's signature checking on firmware zip files. So, even if you take a OTA that has not been rooted, you can simply flash a new recovery that allows you to install su, and use that to restore yourself to a fully rooted system. We have provided ClockworkMod and Amon-Ra recovery images for you to use for this purpose. "
Click to expand...
Click to collapse
Yeah, I don't think we need to revert to original hboot/radio/etc... I think we just need stock recovery and a stock rom to get the OTA
anyone besides the OP tried this yet?
kentoe said:
Yeah, I don't think we need to revert to original hboot/radio/etc... I think we just need stock recovery and a stock rom to get the OTA
Click to expand...
Click to collapse
I would hope this option is the case because I never updated my radio (still on 1.xx), so if I used the method in this thread wouldn't I risk bricking because I'd be flashing the radio on top of itself?
Sent from my Incredible using XDA App
What about reverting everything back if we have S-ON? Sorry if this is a n00b question.
Ruggerxpunk said:
I would hope this option is the case because I never updated my radio (still on 1.xx), so if I used the method in this thread wouldn't I risk bricking because I'd be flashing the radio on top of itself?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Yes, so therefore you wouldn't have to do anything besides going back to a stock rom.
Xxq TZ pxX said:
What about reverting everything back if we have S-ON? Sorry if this is a n00b question.
Click to expand...
Click to collapse
You can use this.
http://forum.xda-developers.com/showthread.php?t=727263
Ruggerxpunk said:
I would hope this option is the case because I never updated my radio (still on 1.xx), so if I used the method in this thread wouldn't I risk bricking because I'd be flashing the radio on top of itself?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
Also know if your rooted with s-on you cannot flash proper otas because the signature check is there and it want allow you to flash a legit signed ota with clockwork. Also know if you accept the ota you will loose root. And won't be able to gain it back without s-off. I really don't understand why people are so apprehensive. Live a little man. It's just a phone. Not a ferrari. Even though it runs like one.
i had a nexus one and was able to unlock the bootloader but i think i updated it to 2.3.4 and then tried to install CWM, which didn't work. i then discovered the antenna was not working correctly so i had to exchange the phone for another new one. once i get my new nexus one i was still thinking about installing CM7 and i just want to get some things straight about 2.3.4 and installing clockworkmod recovery.
will i be able to install CWM after i update my nexus one to stock 2.3.4? if not what is the highest stock build i would be able to do it with?
concerning the radio, if it is not possible to update to 2.3.4 and then install CWM i guess i'd have to update the radio by itself right?
You can unlock the bootloader and install cwm, or you can revert to an earlier version of Android, root, and then install cwm...
so i guess it's not possible to root and install CWM on 2.3.4? what's the latest version of android i would have to revert to for rooting and installing CWM?
There is no exploit for 2.3.4, so there is no easy root...
To downgrade, you have to do the passimg with a shipped image, and the most recent is FRG33. However, once rooted you can update all the way to 2.3.4 and keep root, if you do things in the right order...
You could also update to 2.3.3 and root and update to 2.3.4 keeping root - but the end result is the same...
You can also root 2.3.4 after unlocking the bootloader and flashing a custom recovery. From there, you would need to flash one of the su.zip files floating around (you may need a specific one for Gingerbread), which should remove the stock recovery checks (what replaces the custom recovery when you boot a stock install) and should add the necessary files for root access.
the first nexus one i received was on 2.2.1 so i guess if i plan on installing CM7 i should just keep in there and not bother upgrading anything (maybe the radio only)? just want to make sure where i stand so someone could help me accomplish these things. i know how to unlock the bootloader and i think i'll be fine installing CWM so what order should i:
unlock the bootloader
upgrade the radio (i guess i don't have to do this if i upgrade to 2.3.4)
install CWM
root
upgrade to 2.3.4
install CM7
i'm just making sure i know what i'm doing before i get my replacement nexus one and while i have attempted searching for answers i haven't been able to find the specific order or answer to my question. if anyone can correct any mistakes or assumptions i've been making please let me know.
If you are unlocking the bootloader, there is no need to root the current android install. The whole point of rooting the phone is so you can get the custom recovery on there so you can load CM on the phone. Since you are unlocking the bootloader, you can load the custom recovery using fastboot, then boot into it, wipe the phone and flash CM (and gapps).
And if it is a replacement, it will most likely be running the 5.08 radio, which seems to be the best one for Gingerbread.
So it would be:
Unlock bootloader
flash clockworkmod
boot clockworkmod (select the bootloader screen and then recovery, don't reboot)
wipe phone
flash CM and gapps
reboot
????
profit
DarkKnight62 said:
unlock the bootloader
upgrade the radio (i guess i don't have to do this if i upgrade to 2.3.4)
install CWM
root
upgrade to 2.3.4
install CM7
Click to expand...
Click to collapse
You don't need to upgrade to 2.3.4 unless you want to upgrade the radio and hboot. Of course, you can upgrade them without updating the OS, though upgrading them with OS will be safer.
ok, now that i know that installing CM7 will root my phone if i do it by unlocking the bootloader and installing CWM i am wondering if my phone will be rooted once i restore my nandroid backup that i will make (of stock 2.3.4 android) right before i install CM7?
No. Root is separate from unlocking your bootloader and whatever recovery you are running. Root is at the OS level. Most custom firmwares come pre-rooted. That is, they contain the software needed to allow you to escalate your priveledges to root level. Stock firmwares, do not have this additional software, and anytime you get an update for stock, it will replace everything you had with your previous install, which will make you lose root if you had it.
So, if you install CM7, it will be rooted, but if you restore your stock 2.3.4, it will become unrooted (because it was unrooted when you made the backup).
What is your final plan for software on the phone? Stock 2.3.4, stock 2.3.4 with root, CM7? What is the point of restoring your nandroid of 2.3.4?
Newbie alert again!,
I have identified a few roms I want to test out and my phone is currently operating on the following,
Stock 4.2.2
sense 5.0
software 2.24.161.1
Super cid 11111111
Hboot 156
S-off
Latest trwp recovery.
hypothetically if I was to choose one of the latest ARHD roms (which I would like to consider) could I flash it with my current firmware?
I looked for older versions of ARHD roms to see if there were versions that could avoid me flashing new firmware but there only seems to be the latest update and a Google edition so I am guessing there may be a performance/compatability issue without a newer firmware?
The Rom and Firmware guides appear to be handled separately (which is understandable) but doesnt help a newbie like me make an educated decision,in terms of what firmware to go for...or not to update it at all?
Many guides ignore the firmware side of things or there are suggestions that you can do before or after flashing a rom??but not a joined up part of the process (again I understand the principal of why this is like it is ).
Being seperate threads or processes it is sometimes hard to align forum postings with each other to manually put the process in a list in my mind that is consitent, in date and current.
Cutting to the chase....do I just bite the bullet and upgrade to the specifically associated firmware to the android os/rom build I am going to flash?.?or dont worry about it too much initially?
If i am Supercid... do i only match the phone model number when choosing firmware as I am technically regionally/carrier unlocked?(picking the right one probably troubles me more!)
With s-off as there is no margin for error using the wrong firmware,whereas I have recovery and back ups for the rom side of things.
For me its a bit like riding a bike...i need my stablisers to get my confidence...once i have tried a few solo runs ..i will be fine.. I am sure you have all worn your L plates sorry to burden you with mine...but this forum seems like the safest place to learn !
Shepps
shepppster said:
Newbie alert again!,
I have identified a few roms I want to test out and my phone is currently operating on the following,
Stock 4.2.2
sense 5.0
software 2.24.161.1
Super cid 11111111
Hboot 156
S-off
Latest trwp recovery.
hypothetically if I was to choose one of the latest ARHD roms (which I would like to consider) could I flash it with my current firmware?
I looked for older versions of ARHD roms to see if there were versions that could avoid me flashing new firmware but there only seems to be the latest update and a Google edition so I am guessing there may be a performance/compatability issue without a newer firmware?
The Rom and Firmware guides appear to be handled separately (which is understandable) but doesnt help a newbie like me make an educated decision,in terms of what firmware to go for...or not to update it at all?
Many guides ignore the firmware side of things or there are suggestions that you can do before or after flashing a rom??but not a joined up part of the process (again I understand the principal of why this is like it is ).
Being seperate threads or processes it is sometimes hard to align forum postings with each other to manually put the process in a list in my mind that is consitent, in date and current.
Cutting to the chase....do I just bite the bullet and upgrade to the specifically associated firmware to the android os/rom build I am going to flash?.?or dont worry about it too much initially?
If i am Supercid... do i only match the phone model number when choosing firmware as I am technically regionally/carrier unlocked?(picking the right one probably troubles me more!)
With s-off as there is no margin for error using the wrong firmware,whereas I have recovery and back ups for the rom side of things.
For me its a bit like riding a bike...i need my stablisers to get my confidence...once i have tried a few solo runs ..i will be fine.. I am sure you have all worn your L plates sorry to burden you with mine...but this forum seems like the safest place to learn !
Shepps
Click to expand...
Click to collapse
You are s-off and super cid. Nothing much to worry about here. I'm assuming you are not sprint or verizon. Just get the newest firmware and flash it. If something isn't working right for you flash old firmware. You are not locked down to anything. Here is the newest firmware that will work fine unless you are sprint/verizon/ or dual sim model
https://www.androidfilehost.com/?fid=95897840722644637 - Thanks to LIabtoofer
BACKUP FIRST
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip <--it will say flash again and take longer the second time
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Load newest twrp -http://techerrata.com/browse/twrp2/m7
fastboot flash recovery twrp.img
fastboot erase cache <-- may fail since we wiped cache once already, no biggie
Load twrp "which mounts automatically now" put your rom on phone
wipe, advanced, cache-dalvik,system,data - Wipe <---cache may fail
install new rom. This lollipop firmware works fine with kitkat roms too
an0ther said:
You are s-off and super cid. Nothing much to worry about here. I'm assuming you are not sprint or verizon. Just get the newest firmware and flash it. If something isn't working right for you flash old firmware. You are not locked down to anything. Here is the newest firmware that will work fine unless you are sprint/verizon/ or dual sim model
BACKUP FIRST
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip <--it will say flash again and take longer the second time
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Load newest twrp -
fastboot flash recovery twrp.img
fastboot erase cache <-- may fail since we wiped cache once already, no biggie
Load twrp "which mounts automatically now" put your rom on phone
wipe, advanced, cache-dalvik,system,data - Wipe <---cache may fail
install new rom. This lollipop firmware works fine with kitkat roms too
Click to expand...
Click to collapse
Really appreciate this response and I am not sprint/verzion or dual sim so got that covered.
Just to clarify the rest....
The process of flashing the firmware will completely wipe the phone?
Flash TWRP recovery (i already have this but if the above assumption is correct ,understood!)
Install the new rom...or could I flash my back up (which I have via a OTG lead and memory stick)?
or would the new firmware be incompatible with my old JB 4.2.2 and cause problems?
The only reason I ask is that I could take a breather until I make my decision regarding a new rom.
However u pro's might think just go for it in one its no biggie lol?
Many thanks
Sheppps
shepppster said:
Really appreciate this response and I am not sprint/verzion or dual sim so got that covered.
Just to clarify the rest....
The process of flashing the firmware will completely wipe the phone?
Flash TWRP recovery (i already have this but if the above assumption is correct ,understood!)
Install the new rom...or could I flash my back up (which I have via a OTG lead and memory stick)?
or would the new firmware be incompatible with my old JB 4.2.2 and cause problems?
The only reason I ask is that I could take a breather until I make my decision regarding a new rom.
However u pro's might think just go for it in one its no biggie lol?
Many thanks
Sheppps
Click to expand...
Click to collapse
I do not recommend you just grab the latest firmware update and flash it to you phone, There is a very good chance you will brick your device with a firmware incompatibility
As your on 2.xx firmware jumping strait to 6.xx or 7.xx is a big jump and skipping firmware updates should never be recommended.
To safely update your firmware you need to flash 3.xx, 4.xx, 5.xx and so on untill your updated to the latest firmware. I was able to find the 5.xx and 6.xx firmwares for your device here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/161/ but you will still need to find 3.xx and 4.xx. ALternativly because your s-off with super cid you could switch to a different firmware brand HTC 401 for example. all of which can be found here http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
you will need to flash atleast these 4 updates to get to the latest safely
3.62.401.1
4.19.401.11
5.11.401.10
6.09.401.12
On the other hand if your not comfortable flashing firmware you could just install a Guru Reset rom then update your phone through OTA updates although that will take much longer than flashing the firmware manually. This reset rom will give you stock with working OTA's if installed with the following options http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
Stock Recovery = Yes
Stock Radio =Yes
Root = No
Thanks for that advice,
it did cross my mind that it was a bit of a leap.
If I went back to restoring the stock reovery I know i would lose root and custom recovery and the unlocked status.
Would I have to return to S-on and lose supercid?
TBH getting to s-off was a bit of a nightmare and took a number of tries so I would hate to go through that again?
I might try a phased firmware update unless you recomend a custom rom that will work comfortably with my current firmware?
I prefer the stock look of the ARHD roms...but older versions dont see to be around anymore.
I shall dwell on the situation!
Shepps
shepppster said:
Thanks for that advice,
it did cross my mind that it was a bit of a leap.
If I went back to restoring the stock reovery I know i would lose root and custom recovery and the unlocked status.
Would I have to return to S-on and lose supercid?
TBH getting to s-off was a bit of a nightmare and took a number of tries so I would hate to go through that again?
I might try a phased firmware update unless you recomend a custom rom that will work comfortably with my current firmware?
I prefer the stock look of the ARHD roms...but older versions dont see to be around anymore.
I shall dwell on the situation!
Shepps
Click to expand...
Click to collapse
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
clsA said:
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
Click to expand...
Click to collapse
Heeding your words clsA... I dont want to go through that headache again ..it took me 3 days to get it off with rumrunner (mainly down to the PC's i was using rather than the software) but i dont intend to go back Jack!
clsA said:
NEVER EVER GO S-on ... no matter who says it .. NEVER GO S-on
Click to expand...
Click to collapse
^^^Wise Words^^^ going back to s-on always causes more problems than it solves. Never ever go back to s-on
shepppster said:
Heeding your words clsA... I dont want to go through that headache again ..it took me 3 days to get it off with rumrunner (mainly down to the PC's i was using rather than the software) but i dont intend to go back Jack!
Click to expand...
Click to collapse
You shouldn't shy away from updating your firmware it's really not that scary and perfectly safe as long as you do it correctly. You can even flash modified firmwares. So if you wanted to flash a firmware without losing your custom recovery and boot.img just open the firmware.zip and delete the recovery and boot.img then flash.
below is the basic procedure for flashing a firmware.zip with s-off.
Download the firmware.zip and put it in your fastboot folder on your pc. Boot your phone to the bootloader and connect fastboot usb. In the command window use the following commands to flash the firmware.
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update and will appear to fail. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Danny201281 said:
^^^Wise Words^^^ going back to s-on always causes more problems than it solves. Never ever go back to s-on
You shouldn't shy away from updating your firmware it's really not that scary and perfectly safe as long as you do it correctly. You can even flash modified firmwares. So if you wanted to flash a firmware without losing your custom recovery and boot.img just open the firmware.zip and delete the recovery and boot.img then flash.
below is the basic procedure for flashing a firmware.zip with s-off.
Download the firmware.zip and put it in your fastboot folder on your pc. Boot your phone to the bootloader and connect fastboot usb. In the command window use the following commands to flash the firmware.
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update and will appear to fail. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks for this,I need a bit more clarity.
Delete the two files as described from the zip file,re-zip (package will have hboot,radio,adsp etc).
Flash firmware (do I refer to it by zip name eg3.62.401.1.zip or just as described firmware.zip,although i am guessing one wouldnt actually do anything)
Reboot ,go to recovery (which will be my TWRP) full wipe and flash my back up (or will this revert to my current firmware?) or flash a new rom?
If still using my JB 4.2.2 work with newer firmware? or do I need to start matching the o/s revisions for example 4.3 for the 1st upgrade...move onto the 4.****** firmware next one etc Kit kat rom ?
As I am supercid like you said ,is the alternative firmware ok with my device are these versions just different carrier versions or unsigned or whatever and would there be an isue if i moved to this branch of firmware?
All I really want to do is get my phone to a Kit Kat position...the Guru /ota route seems too convoluted and I am comfortable using fastboot commands but like to have the whole process as water tight as I can get it!
Clearly after the work I gone to to get in a total unlocked state I definitely dont want to go back!
Just to confirm flashing any firmware would not overide my S-off settings that would have to be physically done by command using the appropriate software?
Sorry if you guys are repeating something like this over and over again... best safe and not sorry imo!
Thanks Again
Shepps
shepppster said:
Thanks for this,I need a bit more clarity.
Delete the two files as described from the zip file,re-zip (package will have hboot,radio,adsp etc).
Flash firmware (do I refer to it by zip name eg3.62.401.1.zip or just as described firmware.zip,although i am guessing one wouldnt actually do anything)
Reboot ,go to recovery (which will be my TWRP) full wipe and flash my back up (or will this revert to my current firmware?) or flash a new rom?
If still using my JB 4.2.2 work with newer firmware? or do I need to start matching the o/s revisions for example 4.3 for the 1st upgrade...move onto the 4.****** firmware next one etc Kit kat rom ?
As I am supercid like you said ,is the alternative firmware ok with my device are these versions just different carrier versions or unsigned or whatever and would there be an isue if i moved to this branch of firmware?
All I really want to do is get my phone to a Kit Kat position...the Guru /ota route seems too convoluted and I am comfortable using fastboot commands but like to have the whole process as water tight as I can get it!
Clearly after the work I gone to to get in a total unlocked state I definitely dont want to go back!
Just to confirm flashing any firmware would not overide my S-off settings that would have to be physically done by command using the appropriate software?
Sorry if you guys are repeating something like this over and over again... best safe and not sorry imo!
Thanks Again
Shepps
Click to expand...
Click to collapse
When you flash the firmware.zip the command ends with the actual name of the zip so if the zip is named 3.62.401.1.zip then the correct command would be
Code:
fastboot flash zip 3.62.401.1.zip
The firmware packages are basically the same
3.xx.502.x is AT&T
3.xx401.x is HTC or
3.xx771.x is H3G
and so on, The 3 digit number in the middle is as you suggested just a carrier identifier. Flashing firmware or RUU's will not change your s-off status only you can do that with a very specific fastboot command the chances of it happening accidentally are very slim unless you do it with a toolkit.
So to get to kitkat simply flash the 3.xx 4.xx 5.xx and 6.xx firmware you do not need to flash a matching rom for each firmware version just fastboot reboot-bootloader after each firmware zip the go right to flashing the next one. Once there all done the phone should boot right up regardless of what rom you currently have installed (Provided you removed the boot.img and recovery.img from the zips before flashing) or you can go right to flashing a kitkat based custom rom of your choice if you haven't already. :good:
Danny201281 said:
When you flash the firmware.zip the command ends with the actual name of the zip so if the zip is named 3.62.401.1.zip then the correct command would be
Code:
fastboot flash zip 3.62.401.1.zip
The firmware packages are basically the same
3.xx.502.x is AT&T
3.xx401.x is HTC or
3.xx771.x is H3G
and so on, The 3 digit number in the middle is as you suggested just a carrier identifier. Flashing firmware or RUU's will not change your s-off status only you can do that with a very specific fastboot command the chances of it happening accidentally are very slim unless you do it with a toolkit.
So to get to kitkat simply flash the 3.xx 4.xx 5.xx and 6.xx firmware you do not need to flash a matching rom for each firmware version just fastboot reboot-bootloader after each firmware zip the go right to flashing the next one. Once there all done the phone should boot right up regardless of what rom you currently have installed (Provided you removed the boot.img and recovery.img from the zips before flashing) or you can go right to flashing a kitkat based custom rom of your choice if you haven't already. :good:
Click to expand...
Click to collapse
Great I get that and it makes sense now..but it always pays to check and double check.
My last question is the zips contain radio too,clearly this may or may not be an issue but i would predict they are desgined for certain carriers.The 401 branch I would assume are generic HTC international ones and shouldnt raise an issue unless I went for AT&T whiich is American...and I am in the UK perhaps.
Shepps
shepppster said:
Great I get that and it makes sense now..but it always pays to check and double check.
My last question is the zips contain radio too,clearly this may or may not be an issue but i would predict they are desgined for certain carriers.The 401 branch I would assume are generic HTC international ones and shouldnt raise an issue unless I went for AT&T whiich is American...and I am in the UK perhaps.
Shepps
Click to expand...
Click to collapse
Yeah the HTC 401 firmwares are WWE or World Wide English :good: the radio's shouldnt cause you any problems. And don't worry about asking questions Better to ask before you try. Preventing a brick is easier than fixing one :good:
Danny201281 said:
Yeah the HTC 401 firmwares are WWE or World Wide English :good: the radio's shouldnt cause you any problems. And don't worry about asking questions Better to ask before you try. Preventing a brick is easier than fixing one :good:
Click to expand...
Click to collapse
Well with that invite to ask at least one last question.... I saw the collection of ARHD drivers on this forum state the following? (cant post the link sorry)
"Firmware package from 2.17.401.1 RUU
There are new touch panel drivers inside this firmware that breaks touch in custom recoveries. You can flash it and use only hardware keys in custom recovery or you can remove tp_SYN3202.img from inside the package before flashing."
I would be jumping straight to the 3.******* and upwards but would the same apply delete the same throughout? If it only breaks the custom recovery touch panel I could use a mouse and OTG cable as I assume they are fine in O/S or best to remove the file throughout as it is no big deal.
Finally if there was a beer icon u would get it +thanks.
If you ever need gardening advice just Holla its all i can offer in return for your help and everyone else in this thread lol!:good: (why u might need I dont know ,but u never know lol)
shepppster said:
Well with that invite to ask at least one last question.... I saw the collection of ARHD drivers on this forum state the following? (cant post the link sorry)
"Firmware package from 2.17.401.1 RUU
There are new touch panel drivers inside this firmware that breaks touch in custom recoveries. You can flash it and use only hardware keys in custom recovery or you can remove tp_SYN3202.img from inside the package before flashing."
I would be jumping straight to the 3.******* and upwards but would the same apply delete the same throughout? If it only breaks the custom recovery touch panel I could use a mouse and OTG cable as I assume they are fine in O/S or best to remove the file throughout as it is no big deal.
Finally if there was a beer icon u would get it +thanks.
If you ever need gardening advice just Holla its all i can offer in return for your help and everyone else in this thread lol!:good: (why u might need I dont know ,but u never know lol)
Click to expand...
Click to collapse
You'll be fine the touch screen drivers problem only affects the lower end firmwares. Nothing in the 3.xx upwards to worry about. :good:
Danny201281 said:
You'll be fine the touch screen drivers problem only affects the lower end firmwares. Nothing in the 3.xx upwards to worry about. :good:
Click to expand...
Click to collapse
Thanks again out of curiosity the boot img ,that i would delete from the firmware zip, what does it actually do?
Does it fire up the o/s in the order it needs to launch the phone and as a stock file would expect to see the related o/s system infront of it and flashing a new rom would create a new image for the new set up?
I understand the reason for deleting the recovery file .
and one other thing whilst I intend to use one of the latest customs...if I had problems and flashed my nandroid back up from TWRP would it work using JB 4.2.2? and or would it restore the firmware to the old one too or just restore the o/s so effectiveley i could use my old rom while i looked for another newer one or tried again?
I know my old rom wouldnt optimise the new firmware ,but it would give me time inbetwen tasks if I wanted to do the next step later too.
making mistakes is much easier to resolve the better you understand the logic of the engine so to speak.
Shepps
shepppster said:
Thanks again out of curiosity the boot img ,that i would delete from the firmware zip, what does it actually do?
Does it fire up the o/s in the order it needs to launch the phone and as a stock file would expect to see the related o/s system infront of it and flashing a new rom would create a new image for the new set up?
I understand the reason for deleting the recovery file .
Click to expand...
Click to collapse
You hit the nail on the head there the boot.img is a Rom specific boot launcher if you like. Or otherwise known as the Kernel. If you have a custom Rom and flash a stock firmware the custom boot.img is replaced with the stock boot.img so your custom Rom won't boot. Simply flashing the boot.img from your custom Rom would fix it and all your data will remain in tact but it's just easier to avoid it :good:
and one other thing whilst I intend to use one of the latest customs...if I had problems and flashed my nandroid back up from TWRP would it work using JB 4.2.2? and or would it restore the firmware to the old one too or just restore the o/s so effectiveley i could use my old rom while i looked for another newer one or tried again?
I know my old rom wouldnt optimise the new firmware ,but it would give me time inbetwen tasks if I wanted to do the next step later too.
making mistakes is much easier to resolve the better you understand the logic of the engine so to speak.
Shepps
Click to expand...
Click to collapse
Yes you can downgrade your Rom but keep your newer firmware. It shouldn't cause any major problems. You may find things like reduced no mobile or WiFi signal. Capacitive buttons not working as expected and such but usually everything works ok :good:
Danny201281 said:
You hit the nail on the head there the boot.img is a Rom specific boot launcher if you like. Or otherwise known as the Kernel. If you have a custom Rom and flash a stock firmware the custom boot.img is replaced with the stock boot.img so your custom Rom won't boot. Simply flashing the boot.img from your custom Rom would fix it and all your data will remain in tact but it's just easier to avoid it :good:
Yes you can downgrade your Rom but keep your newer firmware. It shouldn't cause any major problems. You may find things like reduced no mobile or WiFi signal. Capacitive buttons not working as expected and such but usually everything works ok :good:
Click to expand...
Click to collapse
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
shepppster said:
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
Click to expand...
Click to collapse
you don't have to delete anything from the firmware's just flash them sequentially till you get to the last one
then just flash TWRP and your rom to the phone
shepppster said:
I think this is my final question ...I know this has ended up a tutorial but the thread provides good advice to noobies.
I intend to flash the ARHD 84. once i reach the latest firmware.
Will flash each firmware up to 6.09.401.12 deleting the boot img and the recovery in each package.
When I get to firmware 6.09.401.12 I see the rom uses the official firmware so at this point I only need to delete recovery? ...the boot img should be fine for the rom?
Or do I delete the boot image as before as the flash process creates a new boot img.
or I flash the boot img from the custom zip usiing fastboot?(as there is a boot img file in the HD84 zip file)
That is it and sorry for turning this ino a saga,but I think this is a good reference thread in the long run
Shepps
Click to expand...
Click to collapse
If your intention is to flash a rom directly after flashing the firmware then you don't need to worry about the boot.img, the correct boot.img will be flashed with the rom.
It's a good idea to have the rom in your internal storage before you start though so you won't need to boot to android to copy the rom after flashing the firmware or use adb push to get the rom to the phone.
Danny201281 said:
If your intention is to flash a rom directly after flashing the firmware then you don't need to worry about the boot.img, the correct boot.img will be flashed with the rom.
It's a good idea to have the rom in your internal storage before you start though so you won't need to boot to android to copy the rom after flashing the firmware or use adb push to get the rom to the phone.
Click to expand...
Click to collapse
I already have it on my internal memory and also on a USB stick via OTG lead,and in my Fastboot folder (so 3 options).
I Will have to re-install/flash img of TWRP again (if i didnt delete the recovery in the firmware zip files and,as the firmwares will give me stock recovery)- reboot into bootloader launch TWRP recovery find the rom on SD or push in adb or flash from memstick...but job done!
Any issues installing TWRP over an old one? (I intend to use the same version as I have now) I assume it will see the old TWRP folder and old bkup in the SD card too? if not I am goin for it!
Shepps
So I'm currently running BlissPop 5.0.2 and I wanna upgrade to a 5.1 ROM, but I was told I need to update bootloader and Radios, sorry I don't have much experience on this Subject, So what would be the easiest way to update both of these?? Thanx
And say the ROM I'm flashing doesn't work out for me for whatever reason and I need to Restore my nandroid backup (5.0.2 ROM) would I have to downgrade or whatever the bootloader and Radios again?? I'm confused lol thank you
owyheendn said:
So I'm currently running BlissPop 5.0.2 and I wanna upgrade to a 5.1 ROM, but I was told I need to update bootloader and Radios, sorry I don't have much experience on this Subject, So what would be the easiest way to update both of these?? Thanx
And say the ROM I'm flashing doesn't work out for me for whatever reason and I need to Restore my nandroid backup (5.0.2 ROM) would I have to downgrade or whatever the bootloader and Radios again?? I'm confused lol thank you
Click to expand...
Click to collapse
easiest way to update is with fastboot and google images here is link to images https://developers.google.com/android/nexus/images
if you want to keep data or it wont flash follow this http://www.androidpolice.com/2014/11/12/running-into-the-dreaded-missing-system-img-error-flashing-android-5-0-factory-images-heres-how-to-get-around-it/ but you need to erase data because your on a custom rom and it probably wont be compatible with stock rom once you have updated everything reflash a custom recovery or dont flash the stock one at all then flash a 5.1 rom and good to go
What about all the Bootloader and radio zips that can be flashed through TWRP? I've read about people flashing the updates while still being on their 5.0.2 ROMs and everything still works fine, I don't have access to a computer I would like to just update straight from my phone without a Computer if possible? Think I could flash the Bootloader and radio updates through TWRP then reboot n after everything is all good go back and flash the new 5.1 ROM and gapps?
owyheendn said:
What about all the Bootloader and radio zips that can be flashed through TWRP? I've read about people flashing the updates while still being on their 5.0.2 ROMs and everything still works fine, I don't have access to a computer I would like to just update straight from my phone without a Computer if possible? Think I could flash the Bootloader and radio updates through TWRP then reboot n after everything is all good go back and flash the new 5.1 ROM and gapps?
Click to expand...
Click to collapse
i don't know if anyone has twrp flashables for the updating bootloader and radios your searching is as good as mine here i am not experienced with that i always used factory images or ota updates to update those things.
but if you happen to have a backup of your stock rom in twrp you maybe able to just go back to stock then flash back your stock recovery then update with an ota but for an ota to work it has to be all stock no root no nothing just stock.
billycar11 said:
i don't know if anyone has twrp flashables for the updating bootloader and radios your searching is as good as mine here i am not experienced with that i always used factory images or ota updates to update those things.
but if you happen to have a backup of your stock rom in twrp you maybe able to just go back to stock then flash back your stock recovery then update with an ota but for an ota to work it has to be all stock no root no nothing just stock.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3066052
Q&A for [ROM] 5.0.2 Stock-ROM - LG D415 L90
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] 5.0.2 Stock-ROM - LG D415 L90. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
brossovitch said:
Xposed framework crashes the phone.. Testing will not commence..
I never needed it anyway..
Click to expand...
Click to collapse
This is kind of a deal breaker for me, that and the broken rar archive. BUT when it starts working I would like to use your ROM because I love stock roms with minor modifications and debloat. Did you use this xposed framework? http://forum.xda-developers.com/showthread.php?t=3034811
When I flashed the completely stock version, it broke, no data/wifi/bluetooth, and everything crashed. I think it was because I wiped first and since this is an OTA I shouldn't have done that, but now I am worried about trying again, since I just got my phone back up and running. I must say thanks for that, because flashing using TWRP and your ROM gave me TWRP back, so I was able to downgrade back to 410c stock from your ROM. I'll wait for the radio problem to be fixed before I try again.
Hi, I'm new here, but not to android.
imonlyhumanoid said:
This is kind of a deal breaker for me, that and the broken rar archive. BUT when it starts working I would like to use your ROM because I love stock roms with minor modifications and debloat. Did you use this xposed framework? http://forum.xda-developers.com/showthread.php?t=3034811
When I flashed the completely stock version, it broke, no data/wifi/bluetooth, and everything crashed. I think it was because I wiped first and since this is an OTA I shouldn't have done that, but now I am worried about trying again, since I just got my phone back up and running. I must say thanks for that, because flashing using TWRP and your ROM gave me TWRP back, so I was able to downgrade back to 410c stock from your ROM. I'll wait for the radio problem to be fixed before I try again.
Hi, I'm new here, but not to android.
Click to expand...
Click to collapse
You can flash safely with TWRP. Go ahead and upgrade to Stock Lollipop via KDZ then you can try flashing one of brossovitch's ROM. It worked for me. Just follow this http://forum.xda-developers.com/showthread.php?t=3088131 guide if you get broken IMEI or/and Baseband. It will help you get it back as well as get Lollipop on you phone.
Good luck!
So if I read that right, you have to flash the Stock 5.0.2 using TWRP, then flash the Stock 4.4.2 using the LG Flash Tool, then flash the Stock 5.0.2 using the LG Flash Tool, then root then unlock bootloader (is that necessary with the D415? I never did that before) and then use Rashr to flash TWRP and then flash brossovitch's LollipOptimus ROM, just to get the IMEI/Baseband to work? Seems like a lot of hurdles. Why not just flash the 5.0.2 KDZ and then root and flash TWRP possibly with or without bootloader unlocking and then flash the LollipOptimus ROM, or even just flashing it like an OTA from TWRP? Will the LG Official OTA break the IMEI/Baseband?
And has anyone tried the linked Xposed framework?
Thanks for your help!
imonlyhumanoid said:
So if I read that right, you have to flash the Stock 5.0.2 using TWRP, then flash the Stock 4.4.2 using the LG Flash Tool, then flash the Stock 5.0.2 using the LG Flash Tool, then root then unlock bootloader (is that necessary with the D415? I never did that before) and then use Rashr to flash TWRP and then flash brossovitch's LollipOptimus ROM, just to get the IMEI/Baseband to work? Seems like a lot of hurdles. Why not just flash the 5.0.2 KDZ and then root and flash TWRP possibly with or without bootloader unlocking and then flash the LollipOptimus ROM, or even just flashing it like an OTA from TWRP? Will the LG Official OTA break the IMEI/Baseband?
And has anyone tried the linked Xposed framework?
Thanks for your help!
Click to expand...
Click to collapse
No, that is if you had a failed flashed and did not have Stock Download mode which you lose if you unlock the boot loader (which is technically unlocked). Unlocking bootloader is optional, I should put that.
If you have unlocked boot loader then you need to either flash the lag.img or bross's stock ROM with laf.img in it.
imonlyhumanoid said:
So if I read that right, you have to flash the Stock 5.0.2 using TWRP, then flash the Stock 4.4.2 using the LG Flash Tool, then flash the Stock 5.0.2 using the LG Flash Tool, then root then unlock bootloader (is that necessary with the D415? I never did that before) and then use Rashr to flash TWRP and then flash brossovitch's LollipOptimus ROM, just to get the IMEI/Baseband to work? Seems like a lot of hurdles. Why not just flash the 5.0.2 KDZ and then root and flash TWRP possibly with or without bootloader unlocking and then flash the LollipOptimus ROM, or even just flashing it like an OTA from TWRP? Will the LG Official OTA break the IMEI/Baseband?
And has anyone tried the linked Xposed framework?
Thanks for your help!
Click to expand...
Click to collapse
I'm going to try xposed again.
I'm also going to upload the partitions needed to make the bseband work.. There's a way to be easily flash them to go to either.
Stock lollipop is just different. And the custom roms are based on KK. so we gotta be able to go back if we want..
We can.
With L90 utilities you can flash your laf partition or toggle it between fastboot mode & s/w Upgrade (firmware download) mode.
From there you can use adb to flash the proper partitions.
IE:"fastboot flash radio modem.bin"
Which would likely work..
brossovitch said:
With L90 utilities you can flash your laf partition or toggle it between fastboot mode & s/w Upgrade (firmware download) mode.
From there you can use adb to flash the proper partitions.
IE:"fastboot flash radio modem.bin"
Which would likely work..
Click to expand...
Click to collapse
Way cool! Where is this LG L90 tool?
SamsungIsBetterThanApple said:
Way cool! Where is this LG L90 tool?
Click to expand...
Click to collapse
You're on XDA dude.....
....learning to search for and find what you want is a priority..
All I'm going to say, is........ @shinobisoft
May the Droid be with you, young Padawan....:good:
brossovitch said:
You're on XDA dude.....
....learning to search for and find what you want is a priority..
All I'm going to say, is........ @shinobisoft
May the Droid be with you, young Padawan....:good:
Click to expand...
Click to collapse
Haha! Thanks, but just you wait. Soon the student will becoms the master.
SamsungIsBetterThanApple said:
Haha! Thanks, but just you wait. Soon the student will becoms the master.
Click to expand...
Click to collapse
I truly hope so.
When I was young, we had house phones with cords..
Pulse tone hacking is all we had back then.. LOL!
Just restored your latest nandroid and is WORKING GREAT SO FAR !!! Just one thing , how did you guys get rid of the annoying t-mobile voicemail notification ?
Am new to TWRP so excuse me for asking, but since I restored back to 4.4.2 my phone is better than it was before. I would like to upgrade, but I'd like to be able to revert back to 4.4.2 if I have a bad experience. I backed up my phone with TWRP, can I flash the kdz with the LG tool, and then root and get back to TWRP and flash the ROM to make the radio work, and then back up the 5.0.2 ROM and switch between the two?
imonlyhumanoid said:
Am new to TWRP so excuse me for asking, but since I restored back to 4.4.2 my phone is better than it was before. I would like to upgrade, but I'd like to be able to revert back to 4.4.2 if I have a bad experience. I backed up my phone with TWRP, can I flash the kdz with the LG tool, and then root and get back to TWRP and flash the ROM to make the radio work, and then back up the 5.0.2 ROM and switch between the two?
Click to expand...
Click to collapse
Follow this http://forum.xda-developers.com/showthread.php?t=3088131 guide If you have Downlode Mode, skip step 1 and since you are on KK, skip step 3.
Sent from my LollipOptimus™
Since I cannot reply directly to the main thread or the How to fix IMEI/Baseband Unknown Issue (D415) thread, I will ask here.
I am currently running the KitKat stock and rooted, with the original laf.img and TWRP recovery, de-odexed system, and several unwanted stock apps uninstalled.
From my arrangement, to upgrade, I can go to download mode using Vol + and Plug USB (because I haven't zero'd out my laf, right?), and use the 2014 LG tool to flash the Lollipop KDZ. This will cause the data/wifi/bluetooth signals to stop working, as well as losing root and TRWP (correct me if wrong). From there I would need to root and flash back TWRP and then from TWRP flash the LP-[5.0.2]_L90_D415[boot-system-laf-aboot-modem.zip] to get the signals back.
At this point, would I then be at stock rooted lollipop with TWRP and download mode and have a useable phone? If I do a CES flash as recommended, would I lose all of my currently installed apps and data? If so, I should disable xposed first, right?
imonlyhumanoid said:
Since I cannot reply directly to the main thread or the How to fix IMEI/Baseband Unknown Issue (D415) thread, I will ask here.
I am currently running the KitKat stock and rooted, with the original laf.img and TWRP recovery, de-odexed system, and several unwanted stock apps uninstalled.
From my arrangement, to upgrade, I can go to download mode using Vol + and Plug USB (because I haven't zero'd out my laf, right?), and use the 2014 LG tool to flash the Lollipop KDZ. This will cause the data/wifi/bluetooth signals to stop working, as well as losing root and TRWP (correct me if wrong). From there I would need to root and flash back TWRP and then from TWRP flash the LP-[5.0.2]_L90_D415[boot-system-laf-aboot-modem.zip] to get the signals back.
At this point, would I then be at stock rooted lollipop with TWRP and download mode and have a useable phone? If I do a CES flash as recommended, would I lose all of my currently installed apps and data? If so, I should disable xposed first, right?
Click to expand...
Click to collapse
You WILL lose all data but you need to use CES to fix, I believe, the partitions. You DO NOT have to flash the LP-[5.02]_L90_D415[boot-system-laf-aboot-modem.zip] if you go to KK then to L using Lg Flash tool. After succesful Lolli flash, then root, install twrp, and flash one of Bross's rom.
But if I want to go to stock 5.0, with twrp and download mode intact, what do I do? Flash using LG Flash Tool, root and flash twrp and I'm done? This won't cause radio problems?
imonlyhumanoid said:
But if I want to go to stock 5.0, with twrp and download mode intact, what do I do? Flash using LG Flash Tool, root and flash twrp and I'm done? This won't cause radio problems?
Click to expand...
Click to collapse
I promise, if you follow my guide, everything will be fixed. You only lose radio if you flash something wrong. For example, flashing one of bross's ROMs while on kk. That is a bad idea. After you flash to lolli with lg flash tool, you can root and flash twrp. You WILL NOT lose Download Mode unless you zero out the laf by following the Unlocking Boot loader guide.
---------- Post added at 06:24 PM ---------- Previous post was at 06:24 PM ----------
imonlyhumanoid said:
But if I want to go to stock 5.0, with twrp and download mode intact, what do I do? Flash using LG Flash Tool, root and flash twrp and I'm done? This won't cause radio problems?
Click to expand...
Click to collapse
And PLEASE do a CES flash