Hey guys,
I installed last time the unencrypted boot.img to speed things up and yesterday I tried to flash to factory 5.1, but I believe I flashed all images like system, cache, recovery, vendor, but I may have messed up with boot and bootloader. I think I only flashed bootloader and forgot to flash boot, after reboot the device get in a loop, and I can't unlock the bootloader to push the boot.img
Is there a way to push the boot/bootloader.img without needing to unlock the bootloader?
Mephisto_POA said:
Hey guys,
I installed last time the unencrypted boot.img to speed things up and yesterday I tried to flash to factory 5.1, but I believe I flashed all images like system, cache, recovery, vendor, but I may have messed up with boot and bootloader. I think I only flashed bootloader and forgot to flash boot, after reboot the device get in a loop, and I can't unlock the bootloader to push the boot.img
Is there a way to push the boot/bootloader.img without needing to unlock the bootloader?
Click to expand...
Click to collapse
Not if you relocked your bootloader. Time to start the warranty exchange/repair process.
cam30era said:
Not if you relocked your bootloader. Time to start the warranty exchange/repair process.
Click to expand...
Click to collapse
Looks like I'll need to contact Google RMA Monday ...
Related
I've been having a few issues with the root and rom as time has went on. First my fingerprint reader went, then I would have random crashing and shutdowns. Those errors began to get more frequent, and now the internal memory card decided it will wipe itself clean. So I'm done with what ever I had installed. According to the phone that was on April 4th.
I've read some confusing stuff on here about rooting and unrooting, and none of the information is the same. I imagine thats because of all the updates the phone has gone through.
I would like to install cm7 or cm9 since it seems much more stable.
Any help at all to even simply unroot the phone would be appreciated. I need full functionality back.
Atrix 4g
android ver. is 2.2.1
kernel ver is 2.6.32.9
Build number is 1.5.7
Rom: GingerBlur
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
terminator1983 said:
Just wipe data,cache and dalivk from recovery and install which ever rom u want if u have a unlocked bootloader for completely erasing the previous rom u can use fastboot wit these commands.
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
And if u have not unlocked the bootloader check this link first
THE BEGINNERS (N00B) GUIDE!!! N00BS LOOK HERE FOR YOUR HOW TOs
Click to expand...
Click to collapse
Actually, if you want the cleanest and least likely to cause problems method, you should do a full fastboot wipe prior to installing any new ROM. Just wiping data, cache, and dalvik does not give you a completely clean wipe and prep properly for the new ROM.
If you are updating a ROM from a previous release, you are usually OK with just wiping Dalvik and cache. The dev will normally state what to do in their thread.
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
21q said:
Thanks for the replies. How would I be able to check if I've unlocked the boot loader? I did this almost a year ago so I don't remember if I also did that.
Click to expand...
Click to collapse
We couldn't unlock the bootloader a year ago. Was around end of June we had this ability.
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
terminator1983 said:
If ur phone bootloader is unlocked u can see unlocked written on top corner of boot screen logo.
Click to expand...
Click to collapse
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
factory reset/data
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
21q said:
So going off of what you two have said and another thread I looked at. I have time to do this sunday.
First I will unlock the bootloader
then run through these steps
boot to recovery
Wipe Dalvik
wipe cache
boot into fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot
From here I can then load cm7 rom onto my sd card and install it via recovery?
Also, reading further into cm7, it doesnt support he fingerprint reader or web/lap-top huh. Are there any nightly releases that have it? I've seen ONE, but I've been out of this scene too long to really know what good right now.
Click to expand...
Click to collapse
Download CM7.2 RC1 > http://forum.xda-developers.com/showthread.php?t=1556246. It has full FP reader support, both security and navigation. (No webtop though).
After unlocking the bootloader (assuming you will be following these instructions > http://forum.xda-developers.com/showthread.php?t=1136261) You will need root again (instructions also in the previously linked thread), and then you will want to flash Romracers recovery through fastboot before flashing any ROM >
http://forum.xda-developers.com/showthread.php?t=1204500
After this you will be able to get into recovery and flash whatever you want. There is an automated script here for unlocking the bootloader also located here > http://forum.xda-developers.com/showthread.php?t=1182871.
Been a while since I did all this myself, but I think I covered everything!
Good luck.
***Ignore this post***
So I don't need to run any of those fastboot commands??
And should I update my phone to 2.3.4?
I just updated it to 1.8.3 by flashing the sbf so I've lost root and everything.
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
CaelanT said:
Not necessarily. If a SBF has been flashed after unlock, the word "unlocked" is not there.
Click to expand...
Click to collapse
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Does doing a full fastboot wipe delete the cwm recovery?
arpit85 said:
Does it mean u have relocked the bootloader or it is still unlocked ?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I don't believe it was ever unlocked
When I flashed the sbf via rdslite it would go to 100% but would be stuck saying "in process"
I made a new thread though since my problem is completely different now
http://forum.xda-developers.com/showthread.php?t=1568347
21q said:
I ended up flashing using this method
http://forum.xda-developers.com/showthread.php?t=1138204
I used the sbf that was supposed to already have the bootloader unlocked and the do some things for root.
When I went to install romracers though I was getting the error (180002)
From what I have read that means the boot loader wasnt actually unlocked?
So I'm guess I should flash the regular 2.3.4sbf. Then manually unlocked the bootloader myself and then root?
Or could I still manage with whats currently installed some how?
Again thanks in advance for any advice.
Click to expand...
Click to collapse
If you flashed sbf with rsdlite and text unlocked is gone, thats mean that you have relocked BL.
You can unlock again by flashing via RSDLite this:
ATT ONLY(It works for 4.5.91 and 4.5.141- Tested myself yesterday) - http://diamantephoto.com/pudding.rar
It is from post:
http://forum.xda-developers.com/showthread.php?t=1136261
my phone wasnt restoring my backups in twrp recovery and now i have no os and i can only get to bootloader, i relocked my bootloader so i could run ruu but my phone is on the latest version so nothings working, i need help as soon as possible please
kjrehrer said:
my phone wasnt restoring my backups in twrp recovery and now i have no os and i can only get to bootloader, i relocked my bootloader so i could run ruu but my phone is on the latest version so nothings working, i need help as soon as possible please
Click to expand...
Click to collapse
Put TWRP back on. Go into recovery. Keep connected to PC. Transfer a sense ROM and flash it. Assuming you're S-ON: flash MeanBean. Or flash a different sense ROM that has an S-ON installer. Or fastboot flash boot boot.img when you install.
Delakit said:
Put TWRP back on. Go into recovery. Keep connected to PC. Transfer a sense ROM and flash it. Assuming you're S-ON: flash MeanBean. Or flash a different sense ROM that has an S-ON installer. Or fastboot flash boot boot.img when you install.
Click to expand...
Click to collapse
how do i unlock the bootloader again because i relocked it
kjrehrer said:
how do i unlock the bootloader again because i relocked it
Click to expand...
Click to collapse
If you've unlocked the bootloader before then you know how to unlock the bootloader.
Delakit said:
If you've unlocked the bootloader before then you know how to unlock the bootloader.
Click to expand...
Click to collapse
yeah i got it but im putting the mean bean rom on my phone then do i wipe and just flash it?
Delakit said:
If you've unlocked the bootloader before then you know how to unlock the bootloader.
Click to expand...
Click to collapse
when i try to flash it i get "error executing updater binary in zip '/sdcard/meanrom...... error flashing zip" what do i do? every rom i try flashing gives me this error
Unlock the bootloader again, first of all.
Delete your current recovery.img.
Re-download your recovery.
fastboot erase cache
install your recovery again
fastboot erase cache
boot into recovery
when connected you should be able to transfer files from PC to phone.
Otherwise you might need to use USB-OTG I think.
wipe data, cache, delvik/cache, system
Install the ROM.
reboot to bootloader
pull boot.img out of your ROM download
fastboot flash boot boot.img
reboot to system.
Delakit said:
Unlock the bootloader again, first of all.
Delete your current recovery.img.
Re-download your recovery.
fastboot erase cache
install your recovery again
fastboot erase cache
boot into recovery
when connected you should be able to transfer files from PC to phone.
Otherwise you might need to use USB-OTG I think.
wipe data, cache, delvik/cache, system
Install the ROM.
reboot to bootloader
pull boot.img out of your ROM download
fastboot flash boot boot.img
reboot to system.
Click to expand...
Click to collapse
i get an error when i try to flash roms
kjrehrer said:
i get an error when i try to flash roms
Click to expand...
Click to collapse
Lol. I understand that. Not much I can do to help you if you don't try what I already suggested.
Delakit said:
Lol. I understand that. Not much I can do to help you if you don't try what I already suggested.
Click to expand...
Click to collapse
i sent you a direct message about this
Uncheck all options in twrp.
Sent from my EVO using Xparent Skyblue Tapatalk 2
I was flashing latest ota update with TWRP, now last thing i have to do is to flash firmware.zip
wich contains
boot.img
hboot_1.40.0000_signedbyaa.img
rcdata.img
recovery.img
Will i lose any data???
Im trying to get updated 1.17.401.3 with custom recovery, stock rom and root.
Can anyone confirm>??
thanks
IMO, the easiest way to do what you are asking is to just lock the bootloader, reboot into fastboot, and run the RUU.exe. It will update everything. After that, you just re-unlock your boot loader with the unlock.bin you used last time. Then install superSU.zip after you install a recovery. This process gets everything you want and takes about 10-15min.
badtlc said:
IMO, the easiest way to do what you are asking is to just lock the bootloader, reboot into fastboot, and run the RUU.exe. It will update everything. After that, you just re-unlock your boot loader with the unlock.bin you used last time. Then install superSU.zip after you install a recovery. This process gets everything you want and takes about 10-15min.
Click to expand...
Click to collapse
Thanks for your post!
Edit: i mean i have custom recovery TWRP no stock.
But what you said, i will lose data, pictures etc??
and what about my way, will i lose data too?
I flashed the firmware.zip and lost my whole sdcard so i'd back up before doing anything!
edit: you'll need to relock the bootloader to flash it too, which might be what actually wiped everything.
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
geek-x said:
I'm not new to flashing custom roms and rooting Android devices, so I don't think I'm a noob at this. I decided to help my friend unleash the power in his HTC One S by rooting it and giving it a custom recovery, I went through the right processes, Unlocked the phone's bootloader, and flashed the superuser zip and the twrp image, as it didn't seem like a clockworkmod image was compatible with the phone.
I then booted into recovery, wiped/factory reset and then flashed the latest CM11 nightly and got an error in TWRP recovery about the bootloader not been interoperable something like "
Code:
2.15==2.13"
in the error message , fine, I rebooted back into fastboot and checked the HBOOT Version and found out the phone was on HBOOT 1.13 and I think CM11 requires the most recent HBOOT version to work on HTC devices. The phone has got S-Off though.
Now I'm stuck in a bootloop cause I already wiped the OS in TWRP, I have everything in place, the right drivers and all that, I also tried re-installing the stock rom by downloading an HTC One S's RUU file but the device wasn't recognized at all by the RUU installer, I also tried to flash a stock 4.0.x rom as a zip file, no Joy. Now the phone is stuck at the point where it doesn't have an OS to boot into at all.
I'll really appreciate the community's support helping me fix this issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
es0tericcha0s said:
http://forum.xda-developers.com/showthread.php?t=2322755
You need that. Luckily you're already S-Off, so shouldn't be terrible to get going again. Just update the firmware, reinstall TWRP and re-flash CM11. Should be good to go afterwards.
Click to expand...
Click to collapse
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
geek-x said:
Thank you so much for the reply, does it matter that I don't have an OS to boot into as I already wiped and factory reset the phone for installation of a new rom.?
Click to expand...
Click to collapse
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
es0tericcha0s said:
Nah, shouldn't. The firmware we're referring to here is independent of the OS.
Click to expand...
Click to collapse
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
geek-x said:
At the end of the guide, should help fix the issue, there's a part where I'm supposed to install the new CM kernel from the CM .zip package, how do I flash a kernel from Fastboot?
Click to expand...
Click to collapse
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
es0tericcha0s said:
Since you are S-Off, needing fastboot to install the boot.img is not necessary. It will install through recovery.
But, for future reference, you would boot to the bootloader screen, select fastboot, then assuming you have fastboot set up on the PC and the boot.img in the directory of said fastboot, you would use this command:
fastboot flash boot boot.img
then
fastboot reboot
Click to expand...
Click to collapse
I tried flashing the firmware.zip file from the thread but I got a FAILED: (remote: not allowed) error in command prompt at the end of the process, what did I do wrong?
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
UPDATE:
Thank you so much es0tericcha0s, I really appreciate the support, I got the /data mount issue fixed finally. I just had to flash an older twrp recovery image and then reflashed the new one in fastboot and I could then flash CM successfully.
I can't believe I finally unbricked this phone, its been bricked since Sunday. Once again, es0tericcha0s, Thank you!
geek-x said:
UPDATE: I was able to update the bootloader version successfully, as I forgot the part where I was to boot into RUU mode with fastboot oem rebootRUU and worked perfectly the second time.
I rebooted and found out the boot loader was updated to HBoot 2.15, and I also updated twrp to the latest S4 version but now in recovery I get errors about twrp been unable to mount the /data partition. Do I flash another recovery image?
Click to expand...
Click to collapse
You might need to RUU back then. If you have issues with the RUU exe, then you can extract the rom.zip and install it like you did the firmware. There are quite a few tutorials on how to extract it, or there might already be a version floating around for your phone.
Hi everyone,
I just replaced my home security panel into my old sgp311.
It is on stock 5.1.1, just rooted, with locked bootloader.
all things are just going fine and I'm finishing few very end steps, I made a wrong decision, which is install xposed without flashing zip file, I tried to copy/overwrite all the files from the ZIP to system and I thought if I simply make every files with right permission, I won't be messed up, yes I know it is not that easy.
Now I got a bootloop sgp311, I can put it into fastboot or download mode, I tried
Code:
fastboot boot twrp_various_versions.img,
hope it could boot into TWRP recovery and I can flash xposed ZIP and make it come back to earth again but, no.
Is there still a way?
Thanks.
Hak.
etann said:
Hi everyone,
I just replaced my home security panel into my old sgp311.
It is on stock 5.1.1, just rooted, with locked bootloader.
all things are just going fine and I'm finishing few very end steps, I made a wrong decision, which is install xposed without flashing zip file, I tried to copy/overwrite all the files from the ZIP to system and I thought if I simply make every files with right permission, I won't be messed up, yes I know it is not that easy.
Now I got a bootloop sgp311, I can put it into fastboot or download mode, I tried
Code:
fastboot boot twrp_various_versions.img,
hope it could boot into TWRP recovery and I can flash xposed ZIP and make it come back to earth again but, no.
Is there still a way?
Thanks.
Hak.
Click to expand...
Click to collapse
I think you have to reinstall everything from Flashtool (0.9.18.6) or restore with xperia-companion.
fastboot won't flash anything on a locked bootloader. It won't boot afterwards.
Rootk1t said:
I think you have to reinstall everything from Flashtool (0.9.18.6) or restore with xperia-companion.
fastboot won't flash anything on a locked bootloader. It won't boot afterwards.
Click to expand...
Click to collapse
Thank you.
I flashed with flashtool and leave checkbox "wipe userdata" blank, now seems everything but root is untouched.
Hak.