I have bricked my phone trying to install a Rom. The phone is rooted. I tried to flash the older 1.43 boot image. Fastboot showed that it was completed. I restarted and nothing happened. I then tried to flash my backup in twrp. For some reason, the backup did not work. I can still get into HBOOT/FASTBOOT and my recovery.
Is there a way to install a factory image/rom through fastboot?
Or can I install a stock image from my ext sdcard? If so, any have the files?
droid10 said:
I have bricked my phone trying to install a Rom. The phone is rooted. I tried to flash the older 1.43 boot image. Fastboot showed that it was completed. I restarted and nothing happened. I then tried to flash my backup in twrp. For some reason, the backup did not work. I can still get into HBOOT/FASTBOOT and my recovery.
Is there a way to install a factory image/rom through fastboot?
Or can I install a stock image from my ext sdcard? If so, any have the files?
Click to expand...
Click to collapse
Did you try to flash the boot.img again? It could just have been a bad flash. Also, did you check the MD5 sum when you downloaded the old boot.img to verify it wasn't corrupted?
Failing that, you could re-lock your bootloader and flash the RUU listed somewhere in the Development forum.
IceDragon59 said:
Did you try to flash the boot.img again? It could just have been a bad flash. Also, did you check the MD5 sum when you downloaded the old boot.img to verify it wasn't corrupted?
Failing that, you could re-lock your bootloader and flash the RUU listed somewhere in the Development forum.
Click to expand...
Click to collapse
yes and yes. Do i need to re-lock the boot loader or can i just install a rom?
droid10 said:
yes and yes. Do i need to re-lock the boot loader or can i just install a rom?
Click to expand...
Click to collapse
You can try to install another ROM. It may or may not run. If it doesn't, I would re-lock my bootloader, install the new RUU, and go through the root process again. Painful as it may be, it would be my choice.
Better than a $600 dollar paper weight door jam :/ can you fastboot roms like how you can fast boot kernels and radios?
IceDragon59 said:
You can try to install another ROM. It may or may not run. If it doesn't, I would re-lock my bootloader, install the new RUU, and go through the root process again. Painful as it may be, it would be my choice.
Click to expand...
Click to collapse
How do I re-lock my bootloader in install the new RUU? Is the a tool in the DEV section for that?
I believe you have to relock thru the htc dev site.
from my ADR6410LVW using Tapatalk 2
Don't know how but I got it working again. Thanks for help.
droid10 said:
How do I re-lock my bootloader in install the new RUU? Is the a tool in the DEV section for that?
Click to expand...
Click to collapse
I believe it's an adb command you just type relock bootloader. I could be wrong but I know it's something like that.
Sent from my ADR6410LVW using xda app-developers app
spazmcghee said:
I believe it's an adb command you just type relock bootloader. I could be wrong but I know it's something like that.
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
fastboot oem lock is the command
Related
I realize that there are tons of threads about this but I haven't been able to find any that match my setup.
So I S-OFF'd while running the gb firmware, now I want to update to the ics ota firmware so I can run cm9. My question is that do I need to change my hboot after running the ruu, and if so how do I do that? I know these are probably simple questions but I just want to make sure I don't brick my only phone.
Sent from my ADR6425LVW using xda app-developers app
Without having to do the full ruu get these files listed from here http://www.androidfilehost.com/main/-Support_Files-/SuperChilPil/
[ICS][2.25][JB][5-7]PH98IMG.zip - This is radio/pateched hboot combo
&
PH98IMGSTOCKREC.zip This is stock recovery
Updated the radio/hboot with that combo. Then once completed flash the stock recovery and then do a factory reset. Once completed go back into hboot, reflash custom recovery. Then in your custom recovery wipe data/cache then choose your rom.
Snuzzo said:
Updated the radio/hboot with that combo.
Click to expand...
Click to collapse
I do that by renaming it to PH98IMG.zip correct? And I flash the stock recovery by renaming that PH98IMG.zip as well right?
magicnanners said:
I do that by renaming it to PH98IMG.zip correct? And I flash the stock recovery by renaming that PH98IMG.zip as well right?
Click to expand...
Click to collapse
Stock recovery, you can do that or extract it out and fastboot flash. The radio/hboot will need to be renamed.
Snuzzo said:
Stock recovery, you can do that or extract it out and fastboot flash. The radio/hboot will need to be renamed.
Click to expand...
Click to collapse
Awesome thanks I might wait until tomorrow to start all of this because if I don't finish tonight I won't have a phone in the morning lol. But thank you for your help I really appreciate it
magicnanners said:
I realize that there are tons of threads about this but I haven't been able to find any that match my setup.
So I S-OFF'd while running the gb firmware, now I want to update to the ics ota firmware so I can run cm9. My question is that do I need to change my hboot after running the ruu, and if so how do I do that? I know these are probably simple questions but I just want to make sure I don't brick my only phone.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Simple answer would be ....if you are soff. And fastboot is properly setup, then type fast boot OEM lock when you are in fast boot mode. It will lock and reboot. Pull battery. Boot back into bootloader (assuming you have a stock boot loader) and run the latest ics ruu exe. Then once it boots. Enable adb debbuging. Disable quickboot in power setting. Pull battery. Go back to fast boot. HTC dev unlock. You should already still have the unlock token on your pc. Unlock the bootloader. Then fastboot the recovery. Go to the recovery ( I like amon ra) and flash super user. Then reboot...or flash your Rom. All done.
stkiswr said:
Simple answer would be ....if you are soff. And fastboot is properly setup, then type fast boot OEM lock when you are in fast boot mode. It will lock and reboot. Pull battery. Boot back into bootloader (assuming you have a stock boot loader) and run the latest ics ruu exe. Then once it boots. Enable adb debbuging. Disable quickboot in power setting. Pull battery. Go back to fast boot. HTC dev unlock. You should already still have the unlock token on your pc. Unlock the bootloader. Then fastboot the recovery. Go to the recovery ( I like amon ra) and flash super user. Then reboot...or flash your Rom. All done.
Click to expand...
Click to collapse
You don't need to OEM Lock if you're S-Off.
darkghost568 said:
You don't need to OEM Lock if you're S-Off.
Click to expand...
Click to collapse
I'm sorry. I did that and forgot lol. Hell if your s off you can pretty much do what ever.
stkiswr said:
I'm sorry. I did that and forgot lol. Hell if your s off you can pretty much do what ever.
Click to expand...
Click to collapse
Ikr
So I decided to be the lab rat and took the update and tried unlocking bootloader and I confirmed this myself I am unlocking and about to flash kernel and root tools I will post in a few minutes wish results
t1gartist said:
So I decided to be the lab rat and took the update and tried unlocking bootloader and I confirmed this myself I am unlocking and about to flash kernel and root tools I will post in a few minutes wish results
Click to expand...
Click to collapse
It can all be done. did it earlier. all is still good.
I just did the same thing. I updated the firmware going back to stock via RUU and accepting the OTA Update, and re-flashing my original Unlock_code.bin. Now running ViperDNA 1.1.2 with the new firmware just fine.
You do know that since u flashed the venom Rom your back to old firmware?
Check your update the Verizon one will be there again. I did the same thing. Decided to stay stock until venom is updated.
Sent from my HTC6435LVW using xda premium
does anyone know if I flash the current system write kernel, will it undo any of the new update from the OTA?
Not entirely sure, the update flashes a new boot.img, try it and see. U can always revert. It won't hurt anything.
Sent from my HTC6435LVW using xda premium
cmay227 said:
You do know that since u flashed the venom Rom your back to old firmware?
Check your update the Verizon one will be there again. I did the same thing. Decided to stay stock until venom is updated.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Not entirely. I don't have the Rom portion of the new update, but the radio firmware and other portions of the update are still there (the underlying framework). But yeah, I'm not making full use of it until I use a 2.04-based ROM.
sadly i tried 10 times last night it would unlock until rebooted and i would be showed locked again to im not sure what the hell
cmay227 said:
Not entirely sure, the update flashes a new boot.img, try it and see. U can always revert. It won't hurt anything.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
tried flashing the system write kernel, and all hell breaks loose. Its gonna take some time for the dev to incorporate all the changes.
Flashed back to RUU for now.
t1gartist said:
sadly i tried 10 times last night it would unlock until rebooted and i would be showed locked again to im not sure what the hell
Click to expand...
Click to collapse
Are you certain it wasn't 9 times or 11 times?
Turn phone off all the way. Then boot into bootloader and run unlock.bin command.
Sent from my HTC6435LVW using xda premium
Backing up my internal memory guess I'll give it a go what the heck its Friday right?
binzokun said:
tried flashing the system write kernel, and all hell breaks loose. Its gonna take some time for the dev to incorporate all the changes.
Flashed back to RUU for now.
Click to expand...
Click to collapse
Custom kernels won't work on the update?
Here are the steps I took YMMV
Backup Internal Memory
Verify Fastboot and ADB Drivers are properly installed
Boot into Bootloader
RUN "fastboot OEM Lock"
Phone reboots
Run RUU as Administrator
Wait
Boot Device
Connect to WiFi
Run Software Update from Settings
Wait
Install Update
Checked for Updates Again (Nothing)
Copy Unlock_Code.bin to your fastboot directory
ADB Reboot Bootloader
Open command prompt from fastboot directly
Run "fastboot unlock token Unlock_code.bin"
Follow the prompts
Reboot bootloader verify unlocked
Place Recovery.img in fastboot directory
RUN "fastboot flash recovery recovery.img"
Reboot
Copy over Rooted ROM
Reboot into Recovery and flash
Profit
zone23 said:
Here are the steps I took YMMV
Backup Internal Memory
Verify Fastboot and ADB Drivers are properly installed
Boot into Bootloader
RUN "fastboot OEM Lock"
Phone reboots
Run RUU as Administrator
Wait
Boot Device
Connect to WiFi
Run Software Update from Settings
Wait
Install Update
Checked for Updates Again (Nothing)
Copy Unlock_Code.bin to your fastboot directory
ADB Reboot Bootloader
Open command prompt from fastboot directly
Run "fastboot unlock token Unlock_code.bin"
Follow the prompts
Reboot bootloader verify unlocked
Place Recovery.img in fastboot directory
RUN "fastboot flash recovery recovery.img"
Reboot
Copy over Rooted ROM
Reboot into Recovery and flash
Profit
Click to expand...
Click to collapse
Sorry for the noobish question, but will I have to go through such a complex procedure as this if I'm on stock rom, unlocked and rooted? Rooting alone the first time was quite time consuming for me :\
I know I could simply stick with what I have now. I'd really like to have the new firmware though, which supposedly fixes audio and wifi issues.
supertoast92 said:
Sorry for the noobish question, but will I have to go through such a complex procedure as this if I'm on stock rom, unlocked and rooted? Rooting alone the first time was quite time consuming for me :\
Click to expand...
Click to collapse
My suggestion then would be to wait and see if someone comes up with a way to flash the radios. That is the only reason I went through the process.
If I have a backup of stock rooted, do I still have to use RUU?
Will do, thanks!
Word of caution people, once you install the OTA update, your HBoot get updated, so the current RUU stops working. Once you apply the update, there's no going back. All custom kernels don't work, I spend all night trying all of them, the phone just stuck at the boot animation.
I would suggest holding out until all the kernels/custom roms/RUUs are updated, cause if anything goes wrong you have very little tools to work with, especially when we don't have S-Off.
That's good to know. Thank you!
Sent from my HTC DNA
I've been trying to root my EVO 4G LTE using various guides from this board, and I'm not having a lot of luck. I have HBOOT 2.09 and it's S-ON. It seems like the easiest way to root the device is to go S-OFF, but then it appears that the device needs to be rooted to get S-OFF. So I'm a little confused at this point. I've unlocked the bootloader and installed TWRP, but when I try to install the SuperSU root utility it gives me an error about mounting partitions and fails. My bootloader screen also displays "TAMPERED" which seems to be a problem but I'm not having a lot of luck finding a way to resolve it.
So... can anyone tell me what my next step is?
Thanks in advance.
Are you using Facepalm, Moonshine, or DirtyRacun? You haven't really provided enough details to help, at this point. What's your software version? I assume you're running the stock ROM?
I was running the stock ROM, I think it was 3.16. I tried using Facepalm but again it seems like it needs root to work which I haven't been able to achieve just yet. I tried installing the ROM from this thread through TWRP but it just hangs on the HTC screen so I'm not sure what's on there now. I can still get into the bootloader and recovery though.
You can't use Facepalm on 3.16 software. Use Moonshine.
Try flashing this stock rooted to get back to a working state: http://d-h.st/users/Captain_Throwback/?fld_id=10308#files
You may need to fastboot flash the boot.img to make sure it fully boots.
OK, I downloaded that ROM and extracted the boot.img. I booted the phone into the bootloader and ran "fastboot flash boot boot.img". It seems to have completed correctly, no errors at least, but now the phone just sits at the HTC screen with the red text at the bottom. Clearly I'm doing something wrong...
Did you flash the ROM too? Or did it reboot on you when you tried?
I just did the boot.img. Should I also do "fastboot flash zip 3.16.651.3_stock_rooted_odex_CPTB.zip"?
davel23 said:
I just did the boot.img. Should I also do "fastboot flash zip 3.16.651.3_stock_rooted_odex_CPTB.zip"?
Click to expand...
Click to collapse
You have to flash the ROM in recovery.
Ok, so I went into recovery which is still TWRP, adb pushed that ROM to the phone then tried to install it. It gives a bunch of error messages about being unable to mount various items, says it's unable to find path for partition [name of the zip] and fails.
Thanks for your help and patience so far...
You do not extract the file, leave it as a zip and do not open it. Move it to your SD card while in fastboot (mount sd) and from there use twrp and select the correct zip to flash. But above all... DO NOT EXTRACT THE FILR
Sent from my EVO using xda app-developers app
roscoepcoltra said:
You do not extract the file, leave it as a zip and do not open it. Move it to your SD card while in fastboot (mount sd) and from there use twrp and select the correct zip to flash. But above all... DO NOT EXTRACT THE FILR
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
He's S-on. He can't flash kernels from recovery with Hboot 2.09.
davel23 said:
Ok, so I went into recovery which is still TWRP, adb pushed that ROM to the phone then tried to install it. It gives a bunch of error messages about being unable to mount various items, says it's unable to find path for partition [name of the zip] and fails.
Thanks for your help and patience so far...
Click to expand...
Click to collapse
I don't understand what you're doing here. Boot to recovery, mount storage, copy the ROM zip over, and then flash it.
Ok, so I mounted storage from recovery, or least I tried to, my PC said it needed to be formatted. So I did so, copied the file over and flashed it which completed successfully this time. My phone now boots properly, I'll give Moonshine a try now. Hopefully I won't need to bug you again, thanks for all the help.
Captain_Throwback said:
You can't use Facepalm on 3.16 software. Use Moonshine.
Try flashing this stock rooted to get back to a working state: http://d-h.st/users/Captain_Throwback/?fld_id=10308#files
You may need to fastboot flash the boot.img to make sure it fully boots.
Click to expand...
Click to collapse
my friend wants to buy im rooted unlocked evo. it is on viper now can I flash this an it will be stock rooted ?
Tigerstown said:
my friend wants to buy im rooted unlocked evo. it is on viper now can I flash this an it will be stock rooted ?
Click to expand...
Click to collapse
Yes.
Captain_Throwback said:
Yes.
Click to expand...
Click to collapse
S-on Ok? Or do I need to moonshine first?
Tigerstown said:
S-on Ok? Or do I need to moonshine first?
Click to expand...
Click to collapse
You need to use Flash Image GUI or fastboot flash the kernel.
FinZ28 said:
You need to use Flash Image GUI or fastboot flash the kernel.
Click to expand...
Click to collapse
Ok I got that app I use that. An for my other one I'm selling is s-off so I can just flash this on that one..it's been fun on the Evo with the helpful fellow xda's on the jewel. But the wife's work now cover half your bill if you have verizon so we had no choice
Captain_Throwback said:
Yes.
Click to expand...
Click to collapse
Omg I just moonshine(easy thing I ever did) this phone my wife didn't want s-off before. So now I'm s-off I will just flash thanks once again throwback. Hope there is someone in vzw htc one thread that breaks down firmware like you.
Sent from my EVO using XDA Premium 4 mobile app
I'm having a little trouble with Moonshine. It reboots the phone a couple of times, gets to step 3 then just keeps printing periods in the program window. I've been reading through the Moonshine thread and it seems other people have had the same problem, but I haven't seen a solid fix yet. Anyone know what I need to do or should I stick with the Moonshine thread?
Seriously, what the hell is up with this phone? What could be causing this?
Infinityyy said:
Seriously, what the hell is up with this phone? What could be causing this?
Click to expand...
Click to collapse
Did you restore it to stock? With relocked bootloader, phone will only boot with stock configuration (stock boot.img, recovery, ROM).
dansou901 said:
Did you restore it to stock? With relocked bootloader, phone will only boot with stock configuration (stock boot.img, recovery, ROM).
Click to expand...
Click to collapse
I decided to relock it and it started up again. If I have time I will install CWM, flash the stock ROM I found somewhere and relock it. Then flash the boot.img and recovery.img via the windows tool. Would that work? Hopefully. I mean it's not a big deal if it's unlocked, the warranty is gone either way, but still.
Sent from my GT-I9100 using Tapatalk
Infinityyy said:
I decided to relock it and it started up again. If I have time I will install CWM, flash the stock ROM I found somewhere and relock it. Then flash the boot.img and recovery.img via the windows tool. Would that work? Hopefully. I mean it's not a big deal if it's unlocked, the warranty is gone either way, but still.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Should be fine with stock boot.img. Relocked hboot only will boot kernels signed by HTC, but it should boot custom ROM as well if I'm not mistaken (just scratch what I wrote before, important is the boot.img, not the ROM).
Software version 1.54.1540.9 w/Extreme Power Saving... Uploading ota now for folks who need or want it
https://drive.google.com/file/d/0Bx5-C2BrwNVxdjY2WVVsdXBIUzA/edit?usp=sharing
Wonders_Never_Cease said:
Software version 1.54.1540.9 w/Extreme Power Saving... Uploading ota now for folks who need or want it
https://drive.google.com/file/d/0Bx5-C2BrwNVxdjY2WVVsdXBIUzA/edit?usp=sharing
Click to expand...
Click to collapse
Thanks! I hope I can extract the firmware.zip out of this and RUU mode flash it on my Dev. I only want the updated firmware.
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
Wonders_Never_Cease said:
All you have to do after download is pull it outta the ota and flash it as you would any other firmware
Click to expand...
Click to collapse
That's what I thought too, but now i'm hard bricked!!! :crying:
I used fastboot oem rebootRUU and then fastboot flash zip firmware.zip
I updated the firmware in my M7 a few times using this method without incident, but my M8 is now dead...
what was your cid? this was only for developer builds I redid my device twice with it...flashed a complete nand back up and then this ota through stock recovery... did you do the firmware upgrade to 1.54 euro? or any other firmware related flashes?
1 fastboot oem writecid BS_US001
2 fastboot oem readcid
3 fastboot reboot-bootloader
4 fastboot oem rebootRUU
5 fastboot flash zip nameofzip.zip
6 fastboot reboot-bootloader
guyd said:
That's what I thought too, but now i'm hard bricked!!! :crying:
I used fastboot oem rebootRUU and then fastboot flash zip firmware.zip
I updated the firmware in my M7 a few times using this method without incident, but my M8 is now dead...
Click to expand...
Click to collapse
Are you not super cid? When you say hard bricked what is your m8 doing now? Can you get to bootloader. You can't even flash unless you are soff or have true developer edition phone so I would assume you made your phone super cid too?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Wonders_Never_Cease said:
what was your cid? this was only for developer builds I redid my device twice with it...flashed a complete nand back up and then this ota through stock recovery... did you do the firmware upgrade to 1.54 euro? or any other firmware related flashes?
1 fastboot oem writecid BS_US001
2 fastboot oem readcid
3 fastboot reboot-bootloader
4 fastboot oem rebootRUU
5 fastboot flash zip nameofzip.zip
6 fastboot reboot-bootloader
Click to expand...
Click to collapse
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
guyd said:
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
Click to expand...
Click to collapse
Hate to hear that. I'm sure you have already tried this but just in case you haven't. Vol up and power for 10 sec then immediately vol down and power for 5 seconds. Even if you don't see bootloader try fastboot command. Try with and without phone plugged in.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Well sorry to hear this,probably reason it borked your device is it needs the stock recovery i think to finish flashing,didnt look at [email protected] but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.
guyd said:
CID was BS_US002 on a Developer Edition. No firmware upgrades, it was original!!!
I was S-OFF with custom ROM, custom Kernel, and custom Recovery. That's it.
I removed the boot.img and recovery.img out of the zip prior to flashing.
The flash process appeared to work, and nearly all pieces installed successfully.
But after I issued a fastboot reboot, it was dead! No screen, no led, no nothing.
Computer doesn't see it as a device, thus adb or fastboot no longer work.
My first hard brick ever, and I hope my last!
Click to expand...
Click to collapse
an0ther said:
Hate to hear that. I'm sure you have already tried this but just in case you haven't. Vol up and power for 10 sec then immediately vol down and power for 5 seconds. Even if you don't see bootloader try fastboot command. Try with and without phone plugged in
Click to expand...
Click to collapse
Tried those like fifty times! My device is is bricked harder than a diamond...
Wish I knew what exactly happened so I don't do it again. As I said in my previous post, I've done this same thing on my M7 several times without a hitch. Only difference I saw this time was that the RUU flash routine didn't stop after flashing the hboot like it did on my M7 and make me run it one more time to get the rest of the firmware flashed. To be sure I got it all, I flashed it a second time anyway. That was the only difference I saw!
---------- Post added at 09:04 AM ---------- Previous post was at 08:59 AM ----------
Wonders_Never_Cease said:
Well sorry to hear this,probably reason it borked your device is it needs the stock recovery i think to finish flashing,didnt look at [email protected] but that would be my guess...I always flash stock recovery before flashing an ruu or firmware zip.
Click to expand...
Click to collapse
I've ran the RUU flash command on my M7 with a custom recovery several times without incident. Didn't see why it would be any different on the M8, but something is. Wish I would have had an MD5 to verify my download, but it extracted fine so I think it was good.
Only one thing I found that was different from the M7 to the M8.
In the M7 it used hbootpreupdate:3
In the M8 it used hbootpreupdate:12
Wish I knew what this does different.
how did you remove the boot and recovery out of zip? Mine says corrupted when i try to unzip which usually means its encrypted. If you just manually zipped it back up that could be the problem. I don't know what happened and am interested to figure out. At least it is just dead and htc should swap it out no problem.
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Safest way I would suggest is do a restore of a nand backup to completely stock developer build including recovery(1.12.1540.17) and then flash this via stock recovery if you havent gotten the notification after you revert to everything stock...You do not need to relock bootloader if s-off'd...as long as everything else is stock itll flash just fine...Hope this answered your questions about flashing this file.
skhullar said:
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Click to expand...
Click to collapse
Thanks for the guidance.
Lets say a newbie, in his infinite wisdom excitedly rushed to apply a great ROM and failed to create a nand backup of his stock setup... Where would such a bonehead be able to get his hands on a complete nand backup of the stock developer build?
Wonders_Never_Cease said:
Safest way I would suggest is do a restore of a nand backup to completely stock developer build including recovery(1.12.1540.17) and then flash this via stock recovery if you havent gotten the notification after you revert to everything stock...You do not need to relock bootloader if s-off'd...as long as everything else is stock itll flash just fine...Hope this answered your questions about flashing this file.
Click to expand...
Click to collapse
skhullar said:
I'm curious. Sorry if this a silly question, I'm still new to all of this...
Wonders_Never_Cease, So I should flash back to the recoverydevm8.img you provided previously in the A_T_T_Test_1_12_1540_17_ISIS ROM you created first?
Thanks.
Click to expand...
Click to collapse
I would suggest you make your phone super cid before you do any flashing.
Hes already running my rom....Not needed,using brightstar cid works fine as att and developer builds are same mid
an0ther said:
I would suggest you make your phone super cid before you do any flashing.
Click to expand...
Click to collapse
Ill send you a link in the a.m.,lol
skhullar said:
Thanks for the guidance.
Lets say a newbie, in his infinite wisdom excitedly rushed to apply a great ROM and failed to create a nand backup of his stock setup... Where would such a bonehead be able to get his hands on a complete nand backup of the stock developer build?
Click to expand...
Click to collapse
Link and instructions sent...Enjoy
Thank You!
Wonders_Never_Cease said:
Link and instructions sent...Enjoy
Click to expand...
Click to collapse
So no definite way to convert to Dev Edition then I'm guessing, right?