So about 75% of the time when I switch roms I lose my recovery and have to use flashtool to restore kk and root / recovery. Anyone else have that issue?
Sent from my D6603 using Tapatalk
Spz0 said:
So about 75% of the time when I switch roms I lose my recovery and have to use flashtool to restore kk and root / recovery. Anyone else have that issue?
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
Because recovery is installed to system partition on LB so when you change roms you wipe the system and hence lose recovery.
gregbradley said:
Because recovery is installed to system partition on LB so when you change roms you wipe the system and hence lose recovery.
Click to expand...
Click to collapse
K Tha makes sense.
On an addition, the reason I need to flashtool so much is because the phone hangs on the Sony boot screen also 75% of the time. Md5 sums match up before flashing also.
Sent from my D6603 using Tapatalk
I'll elaborate:
Coming from rsxw z5 experience rom, flashing existenz rom. Flashes fine, everything passes, but on reboot it just hangs at kernel boot screen. This has happened multiple times unfortunately, on multiple roms. I'm wondering if there's an issue with the updater script detecting lb or ub? Dunno. I'll check the scripts tonight, but I'm wondering if anyone else has this issue or has worked around it if so.
Cheers
Sent from my D6603 using Tapatalk
Since both of those ROMs are for locked bootloader it will not have anything to do with the updater script looking for UB or LB.
However, if those ROMs are based on stock ROMs that have a different kernel, unless you swap kernels that will result in a boot loop.
Check to see the base version of both those ROMs and ensure you flash the appropriate kernel for the ROMs when swapping between them. Flashing stock kernels can be done via fastboot on locked bootloaders, you only need an unlocked bootloader to flash unsigned kernels.
Related
Update: This bootloader is older and is not the newest available one. If you want the 4.18 version one go to THIS post and flash it with fastboot.
Older bootloader version: Doesn't flash and take hold for everyone, flash at your own risk
Usefull for people that don't want to flash in fastboot. The official OTA for 4.2 flashes this bootloader through recovery in the exact same manner
Code:
md5sum: 7cb16bc418e15ee2c7c48b82ea923e23
Code:
sha1sum: 6151d4afd075d03cfdfa33d111a1a6bba25fcab8
Code:
sha256sum: 2b7efeade37c1ec00d03ba71a56d5b921e6c27d4393298020bcd1601ae079605
Code:
sha512sum: cd7444ec7073e553b7715e4ee30d69f64b06ab3846f1d0ff3d9129f652ab4e90c3400f139a0347f0b78a0719c86b6e2d7f41d36068f032472dbc90c3530cefcb
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
remmyhi said:
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
Click to expand...
Click to collapse
I need to be aware of problems that happens on your Nexus7? I don't have that issue I flashed TWRP Recovery just fine on this booloader...
No, I did not write to you personally. Glad it worked on your side.
Just the people to know.
That's really strange. I would try flashing the 4.1.2 factory images even though it might wipe everything including your sdcard.
Sent from my Nexus 7 using Tapatalk 2
Did that, thanks. Indeed wiped everything
Glad I had a backup
Hey guys,
So, I can flash this file from TWRP and it will upgrade my bootloader?
Thanks in advance!
you can, but make sure you check MD5, flashing a corrupt download can kill your device. OP, you should add a MD5 check in the zip if possible. but thanks for this none the less.
If you have a rom like cm10 installed or other rom that has buysbox in it, just type busybox md5sum /sdcard/bootloader-grouper-4.13.zip
Either in terminal emulator or adb shell.
If your on stock you'll probably want to check it with a program on your pc or install busybox from one of the playstore busybox apps. Of course you'll need to be rooted.
Sent from my Nexus 7 using Tapatalk 2
I went ahead and added sha1sum, sha256sum and sha512sum checks.
I have just flashed the file and thank you, I no longer have to keep my power button pressed for 20 seconds just to have my tablet go on
Thank you so much!!!
If anyone has any problems there is a link in my SIG to fix it or if you just need to revert back...
Just a FYI the older bootloaders are in the factory images! You can extract them out and flash the bootloader separately if you don't want to flash ALL the factory images. So far flashing this with twrp I have not had one single issue yet to speak of... Each bootloader is meant to run on specific platforms, recoveries, kernels ect. So on that note I still suggest if you want to revert your bootloader you revert completely with the factory images.
Sent from my Nexus 7 using Tapatalk 2
Hi,
thanks for that but when i falsh it in TWRP it's wipe all my data but i still have the 3.41 bootloader?
I'm not sure if i understood the thing to do with the md5sum?
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
CWM + CM10 stable
I just flashed this bootloader using CWM 6.0.1.0 and CM10 stable. I used Chrome to download it and the md5sum command in terminal emulator to check the md5 hash before hand. It flashed fine, I have the new version number, everything continues to work. Very easy.
farshad.shirzadii said:
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showpost.php?p=32735541&postcount=5039
Thanks, easy flash, works perfectly
Sent from my Nexus 7 using xda app-developers app
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
blucmal said:
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
When you power your device on you hold the volume down button to get into bootloader. On the main screen it will say what version it is.
Sent from my Nexus 7 using Tapatalk 2
After I obtained s-off I have been having a strange issue where anything using aroma that I flash comes up with a turquoise overlay the entire time and I get install failed each flash, but it seems to fail after everything finalizes and the roms or kernels appear to flash successfully, I haven't had any issues so far.
I guess the question would be, is there a way to clear anything related to aroma? I don't know if it stores something on the sd somewhere, but it remembers my options each time I flash something so it must be stored somewhere
Sent from my HTC One X using Tapatalk 2
probably not, with all the recovery changes and stock jb ota. i would say only use twrp 2.3.3.1 or official cwm. also if you have jb make sure to downgrade your touch panel firmware. anytime you change recovery make sure to "fastboot erase cache" then rewipe cache in recovery that can fix alot of recovery issues. also make sure to wipe everything when changing roms. what rom are you try to flash and what recovery are you using?
I flashed twrp 2.3.3.0 and all is good again. Thanks!
Sent from my HTC One X using Tapatalk 2
Background: I am still on ICS 4.0.4 rooted and unlocked (atleast ez unlock says im unlocked and i have superuser and voodoo says im still rooted) .
However, when I try to flash a custom recovery , ROM manager gets stuck at 100 % and closes. I have also tried installing a custom recovery via EZ recovery, and it says its flashed. However, when I boot into recovery mode, all i see is the stock recovery. So I am not sure what is going on. Do you guys have any idea?
If your still on ICS try selecting an older recovery? Some newer versions are not meant for ICS anymore I believe ...
Sent from my SCH-I535 using xda premium
I recall a similar issue I had due to the bootchain...not sure if that would apply here or not though
I was reading somewhere that samsung devices auto -overwrite a flashed recovery and change it back to stock. I am not sure how to combat this issue , or whether this affects anyone else?
You could try flashing a recovery through odin, that might give a different result. I think when you boot straight into recovery mode from download mode after flashing it might ask you to disable the phone from auto restoring the stock recovery.
I could be wrong though, it seems that's a common thing that happens when rooting a 4.1.1 or 4.1.2 base. However, flashing only the recovery file should still work for an ics base too. Just make sure it's a tar file, not an img file for the custom recovery for use in odin.
Sent from my SCH-I535 using Tapatalk 2
Ok, Ive unlocked my bootloader, installed CWM, rooted my device and checked that it worked, and when I go to the boot loader and select recovery it takes me to CWM. Ive made backups from it and and they restore fine. I even installed a custom kernel and it worked because noFrills let me OC/choose a different governor. Yet from the three ROMs Ive tried so far, they install fine, no errors from CWM, but when I boot up it just gets stuck booting forever. Ive tried wiping everything, Ive tried wiping some things, heck I even tried wiping nothing but I still get the same issue. Id really like to try a new ROM now that I went through the trouble of voiding my warranty, so please try to help me. Thanks in advance, alexbenh
Same here
Gonna try out this guy's method real quick except with CWM
http://forum.xda-developers.com/showpost.php?p=49668571&postcount=5
I know this seems obvious, but are the ROMs you are flashing specific for your device?
Sent from my ST18i using xda app-developers app
yes, I have the Moto G XT1034 and have flashed ROMs before on my old galaxy exhibit and never had any trouble with that
Join the club, same here, done everything right but no custom rom joy for me
Sent from my XT1032 using XDA Premium 4 mobile app
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
WOOOHOOO, I reinstalled the stock 4.4 firmware and everything, I couldnt root it with superboot so I just skipped the rooting step. Then I flashed CWM through the bootloader although I decided to take a risk and instead of "fastboot flash recovery recovery.img", I did "mfastboot flash recovery recovery.img" just to see if it would change anything. Not sure if thats why it works for me now, but its worth a try. Good luck to the rest of you who have this problem.
lowrider262 said:
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Yes, I was already running the stock 4.4 ROM the only differences was that I had a custom kernel which could possibly be an issue, but I wouldnt think so
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
BBOXPT said:
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
Click to expand...
Click to collapse
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
alexbenh said:
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
Click to expand...
Click to collapse
My experience. I tried CWM then loaded a Rom, the first one I tried being CM11 = Bootloop, Then I tried several other Rom's and always the same result, spinning on Bootloop
I then put the phone back to stock firmware 4.4.2 and tried TWRP version TWRP2630, no joy even the bootloader wouldn't work right.
Finally put the phone back to stock AGAIN (now getting frustrated!) and tried installing TWRP2631 using fastboot. That did the trick, now all ROM's load and run fine. This version of TWRP appears to be working well. Backup/restore works, and no problems at all.
Other's report CWM works well, but not for me unfortunately.
Hi All
My E6653 is no longer booting after freezing while running a custom rom. When I boot, it shows the Sony logo, then the light flashes red. It does not let me enter TWRP.
I have tried flashing original firmware using flashtool, repairing using xperia companion and the same issue happens.
I have tried flashing different custom kernels and TWRP versions. The only version of TWRP that works is TWRP 2.8.7.0 by AndroPlus but I cannot access the device through usb and adb does not work.
If anyone has any ideas on how to fix I would be super grateful.
What have u done to make ur device freeze, and which kernel were u using before freezing?
Sent from my E6633 using Tapatalk
shehabskull said:
What have u done to make ur device freeze, and which kernel were u using before freezing?
Sent from my E6633 using Tapatalk
Click to expand...
Click to collapse
Thanks for getting back to me. The phone froze while using the Plex app, and after I force rebooted, the boot issue happened.
I was running V2.3.3 of Xperia X ROM by _LLJY and the kernel that came with that custom rom.
NertySorption said:
Thanks for getting back to me. The phone froze while using the Plex app, and after I force rebooted, the boot issue happened.
I was running V2.3.3 of Xperia X ROM by _LLJY and the kernel that came with that custom rom.
Click to expand...
Click to collapse
Well the Rom's kernel which u were using does not include TWRP, just try one of these solutions :
1/ flash ur original kernel, or reflash ur official firmware using flash tool and DON'T EXCLUDE any thing and wipe user data / apps log... ETC simply do a clean install with out any exclusion
2/ If u have ur original kernel patched with TWRP img inside, directly flash it using flashtool and enter TWRP.
Sent from my E6633 using Tapatalk
shehabskull said:
Well the Rom's kernel which u were using does not include TWRP, just try one of these solutions :
1/ flash ur original kernel, or reflash ur official firmware using flash tool and DON'T EXCLUDE any thing and wipe user data / apps log... ETC simply do a clean install with out any exclusion
2/ If u have ur original kernel patched with TWRP img inside, directly flash it using flashtool and enter TWRP.
Sent from my E6633 using Tapatalk
Click to expand...
Click to collapse
1/ flash ur original kernel, or reflash ur official firmware using flash tool and DON'T EXCLUDE any thing and wipe user data / apps log... ETC simply do a clean install with out any exclusion
- I tried this with 2 different official firmwares and no luck. I made sure I didn't exclude anything. It still gets stuck on the Sony logo
2/ If u have ur original kernel patched with TWRP img inside, directly flash it using flashtool and enter TWRP.
- not 100% sure what to do with this. I don't have the original kernel patched with TWRP img inside. Is this something you have?
NertySorption said:
1/ flash ur original kernel, or reflash ur official firmware using flash tool and DON'T EXCLUDE any thing and wipe user data / apps log... ETC simply do a clean install with out any exclusion
- I tried this with 2 different official firmwares and no luck. I made sure I didn't exclude anything. It still gets stuck on the Sony logo
2/ If u have ur original kernel patched with TWRP img inside, directly flash it using flashtool and enter TWRP.
- not 100% sure what to do with this. I don't have the original kernel patched with TWRP img inside. Is this something you have?
Click to expand...
Click to collapse
Check this :
http://twigstechtips.blogspot.com.eg/2016/04/sony-z5-compact-root-without-losing-ta.html?m=1
At Rooting your Z5 Compact section
Sent from my E6633 using Tapatalk
NertySorption said:
1/ flash ur original kernel, or reflash ur official firmware using flash tool and DON'T EXCLUDE any thing and wipe user data / apps log... ETC simply do a clean install with out any exclusion
- I tried this with 2 different official firmwares and no luck. I made sure I didn't exclude anything. It still gets stuck on the Sony logo
2/ If u have ur original kernel patched with TWRP img inside, directly flash it using flashtool and enter TWRP.
- not 100% sure what to do with this. I don't have the original kernel patched with TWRP img inside. Is this something you have?
Click to expand...
Click to collapse
Try this: Install Androplus kernel and Twrp Recovery which comes with him.
Find flashable prerooted firmware for your model than connect phone to pc to transfer it when you are in Twrp and than wipe cache,dalvik and data and try to flash prerooted zip.
Sent from Xperia Z5
shehabskull said:
Check this :
http://twigstechtips.blogspot.com.eg/2016/04/sony-z5-compact-root-without-losing-ta.html?m=1
At Rooting your Z5 Compact section
Sent from my E6633 using Tapatalk
Click to expand...
Click to collapse
Followed the instructions:
http://twigstechtips.blogspot.com.eg...ng-ta.html?m=1
At Rooting your Z5 Compact section
Still no luck. When the phone turns on, the light goes yellow, I hit:
VOL down - screen goes blank
VOL up - brightness increase of screen then goes off and the light flashes red
Allek84 said:
Try this: Install Androplus kernel and Twrp Recovery which comes with him.
Find flashable prerooted firmware for your model than connect phone to pc to transfer it when you are in Twrp and than wipe cache,dalvik and data and try to flash prerooted zip.
Sent from Xperia Z5
Click to expand...
Click to collapse
Tried this also. kernel and recovery seem to install fine. But when I press VOL up or down, it does not go into twrp.
I managed to get into TWRP using the version from here: http://forum.xda-developers.com/xperia-z5/development/twrp-3-0-2-cm-aosp-roms-t3373008 with AndroPlus kernel. But, cannot access the phones storage through computer. TWRP shows failed to mount /usb-otg (invalid argument).
shehabskull said:
Check this :
http://twigstechtips.blogspot.com.eg/2016/04/sony-z5-compact-root-without-losing-ta.html?m=1
At Rooting your Z5 Compact section
Sent from my E6633 using Tapatalk
Click to expand...
Click to collapse
@shehabskull do you have any other ideas as to what is happening and how to fix? Thanks in advance.
NertySorption said:
@shehabskull do you have any other ideas as to what is happening and how to fix? Thanks in advance.
Click to expand...
Click to collapse
Well really I don't know what's wrong with ur phone... Can u record a video while booting your phone up?
Sent from my E6633 using Tapatalk
shehabskull said:
Well really I don't know what's wrong with ur phone... Can u record a video while booting your phone up?
Sent from my E6633 using Tapatalk
Click to expand...
Click to collapse
Video located here . It keeps doing it over and over. I have never had this happen before and never had an issue which couldn't be resolved with flashing with flashtool.