Unlocked bootloader with fastboot oem unlock
Rooted phone with fastboot by pushing a boot img to it(bexboot.v2.GRK39F_OTA)
Downloaded ics.zip(the partition scheme for ics based roms)
downloaded aokp passion ics rom
downlaoded gapps
Flashed all of them in cwm
But when i boot, it just stays at the aokp unicorn screen.
So far ive gotten back to point A again.
1.) put passimg.zip on sdcard, rebooted with power+down, it restored to stock 2.3.6
2.) Used bexboot boot.img to give me root - http://code.google.com/p/bexboot/
3.) installed rom manager, flashed cwm recovery
4.) Installed Blockrose, via blackrose.exe
5.) booted into cwm, installed ics.zip(which should partition the hboot/blackrose), installed the aokp zip, and the gapps, rebooted.
Stuck on unicorn logo screen again....
I think i need some help now...one thing i noticed, theres no more LOCK icon
1.did you wipe all partitions except sd before and after installing the hboot zip?
2.are you sure that your hnoot partition was changed after applying ics.zip?
Sent from my Nexus One using Tapatalk
Related
I unlocked the bootloader no issues, I installed Clockworkmod did have a bit of an issue with this but eventually it installed. I did a backup, I copied over CM7, I erased etc cleared the dalvic cache or whatever installed zip, rebooted white HTC screen wouldn't budge, restored backup copied over a different CM7 rom same issue, tried a different rom virtuous affinity same issue.
What am I doing wrong?
slugger09 said:
I unlocked the bootloader no issues, I installed Clockworkmod did have a bit of an issue with this but eventually it installed. I did a backup, I copied over CM7, I erased etc cleared the dalvic cache or whatever installed zip, rebooted white HTC screen wouldn't budge, restored backup copied over a different CM7 rom same issue, tried a different rom virtuous affinity same issue.
What am I doing wrong?
Click to expand...
Click to collapse
With the unlocked bootloader, when you flash a custom ROM, you also need to extract the boot.img file from the custom ROM's zip file and place it in the same folder where you run adb.exe and fastboot.exe from.
Then you need to manually flash the boot.img file in FASTBOOT USB mode using the command:
fastboot flash boot boot.img
I've made a mess of this, now my back up won't install, it goes to the HTC screen then reboots and goes in Clockworkmod.
I used the command fastboot flash boot boot.img Instantly is gives FAILED Status malformed
I'm fed up with this I just want back to stock and forget about putting a ROM on HELP??
slugger09 said:
I've made a mess of this, now my back up won't install, it goes to the HTC screen then reboots and goes in Clockworkmod.
I used the command fastboot flash boot boot.img Instantly is gives FAILED Status malformed
I'm fed up with this I just want back to stock and forget about putting a ROM on HELP??
Click to expand...
Click to collapse
Just make sure you're flashing the boot.img from the same rom that you are installing on your phone. I recommend the virtuous.
Also make sure your fastboot is detecting your device
Nonverbose said:
Just make sure you're flashing the boot.img from the same rom that you are installing on your phone. I recommend the virtuous.
Also make sure your fastboot is detecting your device
Click to expand...
Click to collapse
I don't think fastboot is detecting my device, what do I do?
Tried it again and it worked and booted Something just not right with the fastboot, I had a similar issue when unlocking the bootloader, it took several times before it would eventually send.
hi i was trying to root a new o4x, and after everything went right. i unlocked my bootloader by going into bootloader mode and putting "fastboot oem unlock" command, and then chose "unlock it" it said my bootloader is unlocked.
after that i installed cwm touch latest .4.5 ver recovery, and booted in v20a rom, copied vanir rom into my internal sdcard and booted into cwm recovery and tried to flash vanir 4.4.2 rom into it,
after flashing vanir rom, it booted perfectly, but when i connected it to pc, it didn't show my files on internal sdcard which i coppied on it in v20a, i mean there was no vanir rom zip into my internal sdcard, but when i go into recovery and see in "install zip" n go to internal sdcard, it shows vanir rom zip in my internal sdcard.
i thought it's a problem of recovery, so i installed TWRP recovery, i wiped everything including system, and then tried to flash vanir again, and now it's not flashing vanir or any other roms, it says zip successfully installed in recovery, but no rom boot up,
whichever thing i change in TWRP it reset it after rebooting into recovery,
i think TWRP is not able to write anything into system or other drives,
now i'm stuck, i don't know what to do here, i can't flash anything, and my phone is already empty
please help me,
Mr.LOVER said:
hi i was trying to root a new o4x, and after everything went right. i unlocked my bootloader by going into bootloader mode and putting "fastboot oem unlock" command, and then chose "unlock it" it said my bootloader is unlocked.
after that i installed cwm touch latest .4.5 ver recovery, and booted in v20a rom, copied vanir rom into my internal sdcard and booted into cwm recovery and tried to flash vanir 4.4.2 rom into it,
after flashing vanir rom, it booted perfectly, but when i connected it to pc, it didn't show my files on internal sdcard which i coppied on it in v20a, i mean there was no vanir rom zip into my internal sdcard, but when i go into recovery and see in "install zip" n go to internal sdcard, it shows vanir rom zip in my internal sdcard.
i thought it's a problem of recovery, so i installed TWRP recovery, i wiped everything including system, and then tried to flash vanir again, and now it's not flashing vanir or any other roms, it says zip successfully installed in recovery, but no rom boot up,
whichever thing i change in TWRP it reset it after rebooting into recovery,
i think TWRP is not able to write anything into system or other drives,
now i'm stuck, i don't know what to do here, i can't flash anything, and my phone is already empty
please help me,
Click to expand...
Click to collapse
Flash back to Jelly bean just to ensure that all is okay with your phone and start the process of CWM and installing custom rom again.
There is some tut in General section going back to stock via offical LG Flash tool.
Good Luck.
sPEADy said:
Flash back to Jelly bean just to ensure that all is okay with your phone and start the process of CWM and installing custom rom again.
There is some tut in General section going back to stock via offical LG Flash tool.
Good Luck.
Click to expand...
Click to collapse
yeah, thanks, found that, updating firmware through flashing KDZ ...
thanks, will report after doing that
Hello,
Tried rooting my phone with no prior experience. Worked, but eventually I got to where the phone wouldn't boot past splash screen (logo came up, then screen went black while backlight is on and didn't respond to stimuli until battery was removed). Possibly resulted from a build.prop file problem. Did get into boot though, so I fixed that problem by installing a cyanogen rom from a zip file using twrp recovery. I didn't want a custom mod though since I'm used to the look and feel of the 4.0.3 ICS I had, and the cyanogen doesn't seem to have google play so I can't even download anything (original purpose of rooting was to get incompatible apps by spoofing via build.prop file). Currently trying to get back to stock. Unfortunately I didn't make a nandroid backup of the system before the problem occurred, hence I have no backup to flash.
What I tried:
1. Use the official HTC 4.0.3 RUU .exe to upload to the phone. Unfortunately HTC Sync doesn't see this phone, even though I have the correct drivers installed.
2. Attempted to use twrp recovery to install the rom.zip extracted from the RUU directly, the same way I successfully installed the cyanogenmod rom. Failed, claiming it's unable to open zip. The .zip file was checked for integrity and returned by an archiver app.
3. Tried to use these commands from the cmd with phone connected to install the .zip from fastboot:
fastboot erase cache
fastboot oem rebootRuu
fastboot flash zip rom.zip (rom.zip being the functional file of the stock rom)
Failed, saying it's not allowed. Tried it with both locked and unlocked bootloader, no difference.
4. Unzipped the file and tried to flash the system.img file directly, but that failed with a "data length is too large" error.
5. My recovery being twrp 2.1.1, tried looking for altenatives. Can't find any links to download the WCX recovery, but I found several for newer twrp versions, including 2.3.1.0 and 2.6.3.0 which I tried downloading flashing. After flashing the phone got stuck at the cyanogenmod loading logo and wouldn't boot further, and the recovery itself didn't work, just showed the HTC splash, turned black, then booted again normally, getting stuck at the cyanogen logo. Same thing for the 2.6.3.0 version, so I reflashed the original 2.1.1, at which point I can get into recovery but the phone is still stuck at the cyanogenmod during normal boot. At this point I installed the original cyanogenmod .zip from recovery and now at least the phone boots up normally. Still need to get stock back somehow.
Out of ideas and exhausted from this. Any help would be appreciated. Perhaps anyone has a working stock 4.0.3 rom for the Vivid, nandroid backup, etc., or any other ideas. Thanks for reading.
Oh crap...
OK... First... Stock rom can be found in development... Most of the roms there are stock... Read the OP... It'll tell you...
Second... You should use TWRP 2.5.3.0 or something like that I forget...
Third... When you tried the ruu... Did you relock your bootloader...
Side note... Could you get your phone to show up with 'fastboot devices'
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.
all i have now is stock recovery. whats the best way to manually install twrp
go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk
when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.
arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.
simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine
Hi,
I was running Oxygen 4.0.0 and a beta build of TWRP 3.0.3 which works with new encryption. I used the android update mechanics to get the 4.0.1 OTA. System rebooted to recovery, recovery threw an error (zip file corrputed) and since then I am not able to boot the system. Whatever I do I land in TWRP recovery.
Things I did so far:
- Tried installing the full 4.0.1 zip. Install worked without errors, device still boots to recovery.
- Tried to get stock recovery, since another post (https://forum.xda-developers.com/oneplus-3t/help/stuck-recovery-mode-t3532524) indicates stock recovery might fix the problem
--> stock recovery is not obtainable anymore. Seems deleted from all the download links I could find. Example is here: https://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015
- Wipe cache and dalvik cache in the hopes, the instruction to boot to recovery is there somewhere.
I did not do the unbrick tool, since I run linux and didnt want to fiddle with windows yet.
I did make a nandroid backup, so once my system boots again I should be fine.
Any Idea where to either get a mirror of stock recovery or how to fix this problem otherwise?
I had this same problem, and I solved downloading the unbrick tool and extracting the recovery from there. Here is the file
https://drive.google.com/file/d/0BwaafKaXbak3d1RFblFOWVd5eGs/view?usp=sharing
Also locking the bootloader worked for me. Booted into system then unlocked again.
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
mad-murdock said:
Thanks a lot for the stock recovery. That worked!
Once it booted, installing TWRP and SuperSU again.
Click to expand...
Click to collapse
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
mariospizza said:
Does your TWRP boot correctly? I flashed it and when I restarted I still had the stock recovery, so I used fastboot boot and it booted, but it is stuck in the loading screen.
Edit: After rebooting and reflashing totally random, it worked.
Click to expand...
Click to collapse
Yeah, worked totally normal as it should.
My educated guess about this whole dilemma is, the system sets a flag to boot to recovery which TWRP doesn't clear and only stock recovery clears. Usually those flags should be in cache partition, but in this case isn't.
Tldr: don't use build in update mechanisms if you modified Rom and recovery.