Related
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
Hey All,
I've upgraded my 925F to Official MM 6.0.1. Rooted it through kernel Xspace and then installed recovery TWRP_3.0_MM_S6_by_ManhIT
My only concern is when I'm in TWRP I can't reboot, it just freezes.
I can nandroid backup no problem just the reboot part freezes TWRP.
Anyone else had this problem? is there another TWRP to be used?
nb : I tried clearing cache + dalvik, freezes still happen before rebooting.
thanks for ur help.
kaemon said:
Hey All,
I've upgraded my 925F to Official MM 6.0.1. Rooted it through kernel Xspace and then installed recovery TWRP_3.0_MM_S6_by_ManhIT
My only concern is when I'm in TWRP I can't reboot, it just freezes.
I can nandroid backup no problem just the reboot part freezes TWRP.
Anyone else had this problem? is there another TWRP to be used?
nb : I tried clearing cache + dalvik, freezes still happen before rebooting.
thanks for ur help.
Click to expand...
Click to collapse
Try this TWRP form arter... this is the only TWRP being use by many of us here.. you flash it through odin or recovery...
I had the same problem and i solved changing my kernel
Inviato dal mio SM-G925F utilizzando Tapatalk
fabiok81 said:
I had the same problem and i solved changing my kernel
Inviato dal mio SM-G925F utilizzando Tapatalk
Click to expand...
Click to collapse
The issue is not the kernel... its the recovery that doesn't work when reboot to system is touch and is freezing..
Go to advance then terminal
Write reboot
Easy!
Yes i know the iusse is about the recovery but it seems because there is not compatibility between some recovery and some kernel. I tried various recovery 3.0 and i have always a kind of freeze. The TWRP... by Manhit for example gave me freeze with xspace kernel but not with hacker kernel. I don't no the reason....
Inviato dal mio SM-G925F utilizzando Tapatalk
same but different
Hi All,
I'm experiencing a freeze in TWRP after about a few seconds, the whole recovery stands still and this happens every time.
I flashed the Xspace kernel which hasn't help.
The TWRP from arter97 works great, except it doesn't allow me to copy files to my PC using MTP, message says unexpected error.
yet, the ManhIT and Original TWRP allow me to copy data but both of them freeze up after a few seconds which causing the copying to fail.
Reasons I'm doing this is because my SM-G925F start looping and I've tried flashing stock so many times to no avail.
I'm sure all i need to do is data/ factory wipe and my phone will boot fine, I just really need some data before I do that.
Is there perhaps a different kernel I can try?
or if anyone has any suggestions that would be very much appreciated.
Regards
wahwahward said:
Hi All,
I'm experiencing a freeze in TWRP after about a few seconds, the whole recovery stands still and this happens every time.
I flashed the Xspace kernel which hasn't help.
The TWRP from arter97 works great, except it doesn't allow me to copy files to my PC using MTP, message says unexpected error.
yet, the ManhIT and Original TWRP allow me to copy data but both of them freeze up after a few seconds which causing the copying to fail.
Reasons I'm doing this is because my SM-G925F start looping and I've tried flashing stock so many times to no avail.
I'm sure all i need to do is data/ factory wipe and my phone will boot fine, I just really need some data before I do that.
Is there perhaps a different kernel I can try?
or if anyone has any suggestions that would be very much appreciated.
Regards
Click to expand...
Click to collapse
Try with hacker kernel. Wipe cache but not data
callumbr1 said:
Try with hacker kernel. Wipe cache but not data
Click to expand...
Click to collapse
Thanks for your response callumbr1.
I've attempted two different kernels:
g925-hacker-echoe-kernel-V14.zip
hacker-kernel-S6-Universal-V12.zip
Above mentioned problems persist.
Since arter97 TWRP is not freezing on me, if I run a back up on the Data only. Then perform the wipe, the backup should still be there, correct?
and lets say I flash the stock ROM again if necessary and I'm able to boot the device.
Would it be possible to restore that data back up at all ?
or perhaps copy that back up to my PC and access/extract the files with a separate application?
Many Thanks
wahwahward said:
Thanks for your response callumbr1.
I've attempted two different kernels:
g925-hacker-echoe-kernel-V14.zip
hacker-kernel-S6-Universal-V12.zip
Above mentioned problems persist.
Since arter97 TWRP is not freezing on me, if I run a back up on the Data only. Then perform the wipe, the backup should still be there, correct?
and lets say I flash the stock ROM again if necessary and I'm able to boot the device.
Would it be possible to restore that data back up at all ?
or perhaps copy that back up to my PC and access/extract the files with a separate application?
Many Thanks
Click to expand...
Click to collapse
I think best thing to do is get an otg storage adapter that plugs direct to phone. They are cheap.
Then run the backup of data and store on otg storage. Then you have it safe and it can be restored at a later time with restore option in twrp.
Or you can always do a full nandroid backup.
Can you get onto the phone now? Does it boot up?
Is there anything specific you need off the phone? To be backed up?
callumbr1 said:
I think best thing to do is get an otg storage adapter that plugs direct to phone. They are cheap.
Then run the backup of data and store on otg storage. Then you have it safe and it can be restored at a later time with restore option in twrp.
Or you can always do a full nandroid backup.
Can you get onto the phone now? Does it boot up?
Is there anything specific you need off the phone? To be backed up?
Click to expand...
Click to collapse
I plan on getting one of those, they seem extremely useful. A colleague has one which I plan to use tomorrow if they remember to bring it, I will then do as you suggest.
Never done a full nandroid back up before but will do some searching on that.
Phone still hangs at the Samsung splash screen.
And its really only pictures and some videos that I want, contacts would be nice too.
PS, this happened when I plugged my device into the PC to charge it was at about 5%, and I was making use of side sync to control the device when it just shutdown. I thought maybe the battery died so left it to charge a bit, it eventually tried to boot up by itself and its been looping ever since. Was really strange cause it gave me no issues prior to this. When I tried to get to the recovery it would hang at the "installing updates" section once I flashed the stock ROM I was able to get to recovery to wipe the cache but no luck.
Thanks for your suggestions much appreciated.
wahwahward said:
I plan on getting one of those, they seem extremely useful. A colleague has one which I plan to use tomorrow if they remember to bring it, I will then do as you suggest.
Never done a full nandroid back up before but will do some searching on that.
Phone still hangs at the Samsung splash screen.
And its really only pictures and some videos that I want, contacts would be nice too.
PS, this happened when I plugged my device into the PC to charge it was at about 5%, and I was making use of side sync to control the device when it just shutdown. I thought maybe the battery died so left it to charge a bit, it eventually tried to boot up by itself and its been looping ever since. Was really strange cause it gave me no issues prior to this. When I tried to get to the recovery it would hang at the "installing updates" section once I flashed the stock ROM I was able to get to recovery to wipe the cache but no luck.
Thanks for your suggestions much appreciated.
Click to expand...
Click to collapse
They are really useful, one of the best things ive ever bought regarding my phone. I use it daily now.
As for nandroid backup, it basically backs up absolutely everything including the firmware and data and all partitions. I always do it before flashing or modifying anything. Then if anything goes wrong, you just flash back your nandroid backup.
Can i ask before this happened did you use google photos? If so and sync was on they will all be saved. If you dont use it i reccomend you to use it from now on incase this ever happens in future.
See how you go making the backup when you can then if you need help regarding flashing the stock and getting the phone working ill help
callumbr1 said:
They are really useful, one of the best things ive ever bought regarding my phone. I use it daily now.
As for nandroid backup, it basically backs up absolutely everything including the firmware and data and all partitions. I always do it before flashing or modifying anything. Then if anything goes wrong, you just flash back your nandroid backup.
Can i ask before this happened did you use google photos? If so and sync was on they will all be saved. If you dont use it i reccomend you to use it from now on incase this ever happens in future.
See how you go making the backup when you can then if you need help regarding flashing the stock and getting the phone working ill help
Click to expand...
Click to collapse
Good day callumbr1
I never made use of google photos, not the biggest fan of cloud storage to be completely honest but I do see its benefits when it comes to times like these. lol
as for the device, last night I flashed a custom recovery (arter97) and made use of the SkipSoft Android ToolKit to pull my photos, videos and documents through the adb protocol. That being said, I have the data I wanted so all is well there.
However, after wiping the cache and doing a data / factory reset. I reflashed the stock ROM, it all goes swell until the android pops up with a message displaying " installing system updates". It gets to 32% changes to erasing then restarts , and this happens constantly no matter how many times I flash it or restart the device.
I read on another forum that my devices is probably dead and it could be the mother board. Any thoughts?
You think maybe a custom ROM would bring it up?
wahwahward said:
Good day callumbr1
I never made use of google photos, not the biggest fan of cloud storage to be completely honest but I do see its benefits when it comes to times like these. lol
as for the device, last night I flashed a custom recovery (arter97) and made use of the SkipSoft Android ToolKit to pull my photos, videos and documents through the adb protocol. That being said, I have the data I wanted so all is well there.
However, after wiping the cache and doing a data / factory reset. I reflashed the stock ROM, it all goes swell until the android pops up with a message displaying " installing system updates". It gets to 32% changes to erasing then restarts , and this happens constantly no matter how many times I flash it or restart the device.
I read on another forum that my devices is probably dead and it could be the mother board. Any thoughts?
You think maybe a custom ROM would bring it up?
Click to expand...
Click to collapse
Thats good about your data :good:
As for the little android guy and the installing updates then erasing, this normally happens. It happens every single time i restore and normally boots fine just after its not normally an issue. After yours says erasing does it then just reboot and restart the process of erasing constantly?
What i would suggest first is to flash a different stock ROM, preferably one with newest bootloader.
After flashing, boot to recovery and wipe dalvik cache. If it gets as far as the samsung logo just leave it as the first boot can take a while... like 30 minutes.
If that doesnt work try to flash a custom ROM. I reccomend CarHD ROM. I uave used it for quite some time and no issues.
It deffinately does not sound like motherboard issue. Normally you would have many issues and errors on boot prior to having main board issues.
See how you get on and keep me updated.
callumbr1 said:
Thats good about your data :good:
As for the little android guy and the installing updates then erasing, this normally happens. It happens every single time i restore and normally boots fine just after its not normally an issue. After yours says erasing does it then just reboot and restart the process of erasing constantly?
What i would suggest first is to flash a different stock ROM, preferably one with newest bootloader.
After flashing, boot to recovery and wipe dalvik cache. If it gets as far as the samsung logo just leave it as the first boot can take a while... like 30 minutes.
If that doesnt work try to flash a custom ROM. I reccomend CarHD ROM. I uave used it for quite some time and no issues.
It deffinately does not sound like motherboard issue. Normally you would have many issues and errors on boot prior to having main board issues.
See how you get on and keep me updated.
Click to expand...
Click to collapse
It doesn't say erasing after the first time. Right after the flash it will reboot to the blue screen with the android, it displays Installing update with a percentage bar which gets to 32% then that disappears and shows erasing, then again it shows installing update with no percentage bar. The android guy has a two arrows on his chest spinning which eventually stops. The device then reboots. It goes back to the Android guy but this time it shows "installing system update" without the percentage bar, it will then freeze again then reboot. That will continue forever until the battery dies.
After flashing though I can't seem to get to recovery to wipe the cache, I hit the buttons as I always do, but the blue screen and android always appears.
This is the stock ROM I'm currently using:
https://www.sammobile.com/firmwares/download/105085/G925FXXU4DPJB_G925FXFV4DPJ2_XFV/
Do you perhaps have a link to that custom ROM? would it work fine with the service provider here in SA (Vodacom) ?
And well at least that is some good news, I'm not too keen on having to take this into a shop and pay for parts.
wahwahward said:
It doesn't say erasing after the first time. Right after the flash it will reboot to the blue screen with the android, it displays Installing update with a percentage bar which gets to 32% then that disappears and shows erasing, then again it shows installing update with no percentage bar. The android guy has a two arrows on his chest spinning which eventually stops. The device then reboots. It goes back to the Android guy but this time it shows "installing system update" without the percentage bar, it will then freeze again then reboot. That will continue forever until the battery dies.
After flashing though I can't seem to get to recovery to wipe the cache, I hit the buttons as I always do, but the blue screen and android always appears.
This is the stock ROM I'm currently using:
https://www.sammobile.com/firmwares/download/105085/G925FXXU4DPJB_G925FXFV4DPJ2_XFV/
Do you perhaps have a link to that custom ROM? would it work fine with the service provider here in SA (Vodacom) ?
And well at least that is some good news, I'm not too keen on having to take this into a shop and pay for parts.
Click to expand...
Click to collapse
Thats pretty much exactly what happens to mine after restoring or flashing but mine boots up.
Flash the firmware again but in odin options uncheck auto reboot. This time after flashing, the phone should stay off. Then you can boot to recovery.
If that doesnt work, whilst it is on the blue screen with android guy hold only vol down and power, phone will reboot, as soon as the screen goes off switch to recovery combo and this should force it to recovery.
https://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519/page1427
Here is the link to custom ROM, it will work fine on your phone. You need to flash this through TWRP. If you need steps on how to do this please tell me.
callumbr1 said:
Thats pretty much exactly what happens to mine after restoring or flashing but mine boots up.
Flash the firmware again but in odin options uncheck auto reboot. This time after flashing, the phone should stay off. Then you can boot to recovery.
If that doesnt work, whilst it is on the blue screen with android guy hold only vol down and power, phone will reboot, as soon as the screen goes off switch to recovery combo and this should force it to recovery.
https://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519/page1427
Here is the link to custom ROM, it will work fine on your phone. You need to flash this through TWRP. If you need steps on how to do this please tell me.
Click to expand...
Click to collapse
Man I think I'm just going to try the custom to see if it works.
Would I need to flash a custom kernel or can it be stock?
After flashing the kernel with twrp I'm going to assume I would follow the same step.
1. flash TWRP custom recovery
2. copy .zip file to sdcard
3. go to recovery, install , select the .zip
Is that it or am I missing anything else when it comes to flashing ROMs through the recovery?
wahwahward said:
Man I think I'm just going to try the custom to see if it works.
Would I need to flash a custom kernel or can it be stock?
After flashing the kernel with twrp I'm going to assume I would follow the same step.
1. flash TWRP custom recovery
2. copy .zip file to sdcard
3. go to recovery, install , select the .zip
Is that it or am I missing anything else when it comes to flashing ROMs through the recovery?
Click to expand...
Click to collapse
Thats it.
Before installing rom go to wipe in TWRP, wipe data, dalvik, cache and system.
You dont need to flash a kernel though.
However when flashing carhd rom aroma installer will go through some choices, from there you can choose to install arter kernel. I reccomend doing this rather than keeping stock kernel.
Remember once installer complete and rom is installed leave it a while if it hangs on samsung logo screen. It can take a while to boot.
callumbr1 said:
Thats it.
Before installing rom go to wipe in TWRP, wipe data, dalvik, cache and system.
You dont need to flash a kernel though.
However when flashing carhd rom aroma installer will go through some choices, from there you can choose to install arter kernel. I reccomend doing this rather than keeping stock kernel.
Remember once installer complete and rom is installed leave it a while if it hangs on samsung logo screen. It can take a while to boot.
Click to expand...
Click to collapse
Currently waiting on the custom to download, don't have the quickest internet connection.
while I've been waiting, I've tried the stock ROM again.
something I forgot to mention before, which has happened a few times:
During the blue screen with the droid stating installing updates.
it switches to a screen with a big yellow triangle two dots below it and a dead droid.
After this I get to recovery, I wiped the cache and its getting to the samsung logo but freezes and then restarts all over again.
I'm just curious if you know what the yellow triangle thing means?
wahwahward said:
Currently waiting on the custom to download, don't have the quickest internet connection.
while I've been waiting, I've tried the stock ROM again.
something I forgot to mention before, which has happened a few times:
During the blue screen with the droid stating installing updates.
it switches to a screen with a big yellow triangle two dots below it and a dead droid.
After this I get to recovery, I wiped the cache and its getting to the samsung logo but freezes and then restarts all over again.
I'm just curious if you know what the yellow triangle thing means?
Click to expand...
Click to collapse
I think it normally means a failed update. Sometimes there are instructions to use smart switch other times it just means the update failed.
Try with the custom ROM and keep me updated.
Here's what I did with a new T-Mobile Samsung Galaxy S5:
- Started phone in download mode (started it with Volume Down, Home, and Power buttons) and connected it to computer.
- Started Odin3v185, saw yellow COM box.
- Clicked PDA button and selected philz_touch_6.26.2-klte.tar.md5 file.
- Clicked Start button, flashing went fine, phone reset and everything was cool, still with stock ROM. I was able to boot into Philz recovery to verify that flashing worked.
- As part of my goal of installing XtreStoLite ROM 2.2 (Lollipop), the following steps were to install the modem and bootloader for that ROM.
- Started phone in download mode and connected it to computer.
- Started Odin3.09, saw blue COM box.
- Clicked BL button, and selected G900T-LP-UVU1DOB1-BOOTLOADER.tar.md5.
- Clicked CP button, and selected G900T-LP-UVU1DOB1-MODEM.tar.md5.
- Clicked Start to flash. Phone reset, but it froze at the Samsung logo.
I gave it about a half hour just to make sure it wasn't just taking it's time with this first boot after the update, but it stayed at the Samsung logo. Only way to turn it off was to remove the battery. I'm still able to boot into Philz, so I figured a way to fix it might be to just go ahead and install the ROM. So I selected the "install from zip" option and installed XtreStoLite_ROM_v2.2_LP_XXU1BOD3.zip. Now the startup logo is a bit different, but it still stays frozen at the logo. I know from previous times installing this ROM that it does usually take awhile (maybe 5 minutes) on the first boot after installing, but I let it sit again for about 30 minutes with no luck.
The only thing I can see that I did differently this time, which I know realize was dumb, was skipping the step after flashing Philz where I boot into it and install UPDATE-SuperSU-v2.37.zip to root the device. I thought that I'd be able to install the bootloader, modem, and ROM and end up with a rooted OS, but I'm guessing that rooting is separate from those things, and they can't succeed until the phone has been rooted.
So... what can I do now? I'm trying to install the stock ROM (G900T_TMB_G900TUVU1CNK2_G900TTMB1CNK2_original.zip), but Philz gives me a "installation aborted" error before it even starts, with no other error messages. I also suspect I should install the original kitkat bootloader+modem, but I'm not sure where to find those (searching yields a lot of different results).
Any help would be greatly appreciated. Thanks!
The bootloop must be related to the bootloader/modem you've flashed. SU will allow root access once booted, but it won't prevent the system from booting if you skip it. Are you simply trying to root? FWIW, I'd recommend skipping Lollipop altogether, Marshmallow is night and day better than Lollipop. Flash the complete factory image of one of the Marshmallow releases, then flash your recovery and install SU. There are a couple of good, debloated Marshmallow roms available.
I was able to get out of the situation by flashing a stock ROM from here:
http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
I first flashed the stock modem and bootloader, though I'm not sure that was required because I think they're included in the ROM itself.
Used the latest 4.4.2 ROM and NK2 bootloader+modem, just because I'm pretty sure it was 4.4.2 that was on the phone when I got it.
Retried my procedure, this time rooting + disabling KNOX before flashing the Lollipop bootloader+modem from the ROM's install instructions, but I still ran into the same "freeze at boot" problem. I don't know what could be the issue, as I've done this exact procedure with two previous S5s. Not really looking to check out Marshmallow ROMs, just because I'm short on time these days, and after trying out a handful over the years, the XtreStoLite is by far the best for me.... really the perfect combo of stock Android with some of the improvements offered by TouchWiz, with all the tweaks to fix annoying "features" that I want fixed (for example, the removal of that damn "are you sure you want to increase the volume? It could damage your hearing" warning when you connect headphones and try to turn up the volume). Also, just stable and fast, compared to most/all the others I've tried.
Sounds to me as if you need stock Marshmallow with a custom recovery and Exposed. Mine is fast as hell, extremely frugal on battery, and Exposed has got rid of all the annoying TW "features", like the volume warning you mention (also, expanded notifications on lockscreen, battery full notification gone, circle battery, etc, etc). There are also alternatives to stock that are good, I tried one a couple of weeks ago that I think I'm probably going to go back to. Lollipop is horrible after using KitKat, Marshmallow brings back the KitKat experience but with dramatically improved battery life. You'll also get some Stagefright improvements.
Sorry for the delayed response, been too busy to deal with this for a couple weeks. How exactly do I get a stock Marshmallow with custom recovery and Exposed? Don't I already have the custom recovery covered with Philz? What Marshmallow ROM would you recommend? Thanks for the feedback!
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
invisiblewave said:
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
Click to expand...
Click to collapse
Did you deodex GPI1 before exposed?
invisiblewave said:
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
Click to expand...
Click to collapse
Does this thread have the info I need for installing Xposed (I'm assuming "Exposed" and "Xposed" are the same thing)?
http://forum.xda-developers.com/showthread.php?t=3034811
Just install a .zip from TWRP, then install the .apk to manage installed modules?
I have "UPDATE-SuperSU-v2.37.zip". Is that sufficient for SU?
Well dammit, I've now spent multiple hours I didn't have trying to get *ANY* ROM other than the stock KitKat one to work. Was just about to give up after trying one last time with XtreStoLite, this time using KToonsez kernel instead of stock. Restarted and it was taking forever to boot, so I assumed it was frozen and was about to pull the battery and call it a night, when it actually made it into the OS! So perhaps there's something going on with the phone that won't let it boot with any stock kernel, other than 4.4.2. Bummer, because I was starting to get excited about trying Marshmallow.
It's because you have KitKat firmware. You just need to flash the entire MM package first.
What is the MM package, if it's not
G900T-(GPI1)-Bootloader.tar
G900T-(GPI1)-Modem-NonHLOS.tar
G900TUVS1GPI1_G900TTMB1GPI1_G900TUVS1GPI1_HOME.tar.md5
?
You don't need to flash the bootloader & modem separately. If you download the complete firmware, that's all you need to flash, it has all the necessary partitions in it. Just flash that, see if it works, then flash the recovery, etc.
I already tried G900TUVS1GPI1_G900TTMB1GPI1_G900TUVS1GPI1_HOME.tar.md5, both with and without the bootloader+modem packages.
I didn't see any mention of you having tried it in your earlier post. You should be able to flash just that package under AP (All Partitions, I assume), and it should install all the partitions it finds inside the tar. My guess is that Odin isn't completing correctly. What does it say in the log on the left? I had to use Odin 9, 10 wouldn't work on my setup for some reason, nor could I get it to work on XP, only on Windoze 8.
I've been using CM13 on my phone for a long while, but it was heavily bugged (my camera kept crashing, I've kept losing cell reception, couldn't receive calls etc), so I finally decided to try another ROM. I've heard good things about ResurrectionRemix ROMs, so I've decided to give it a try. I did factory reset and wiped cache (using CWM 6. something) and flashed RR 7.1 along with the appropriate gapps and rebooted the phone. It's worth noting that I've put the ROM and Gapps zip files on USB stick and connected it to the phone via micro USB cable. It all went smoothly, and the phone booted right up. However, once I got into the startup setting and choosing the language suddenly it just rebooted all on its own. Same thing happened 2 more times, and I got stuck in a bootloop after that.
So I figured I should flash another ROM, and I wanted to give RR 6.0 a try. I've downloaded it and saved it to my USB stick, however, when I tried to flash any zip files from my stick, it just kept randomly unmounting, disrupting the process, giving me "USBdisc0 idle-unmounted" message. Since I don't have an SD card, only thing I could do was push files to my phone, and I've managed to do so via Quick ADB Pusher. This time, flashing went without a hitch, however, I've tried cleaning my phone completely (formatting all the data and system files), and I think I messed it up a bit when I did that, since I didn't flash SuperSU along with ROP and gapps. Again, I got stuck in a bootloop without any signs of the ROM working.
So I decided to flash CM13 again. At least I was sure it was working on my phone, and I figured it was better to have a crappy phone than no phone at all. So I pushed the CM13 file onto the phone and flashed it, but still got stuck in bootloop. I finally remembered about SuperSU and tried to flash it too, but now my phone kept restarting in the middle of the flashing process. I've tried doing the factory reset and cache wipe, but I can't flash any files now without it restarting only few seconds into the process.
I have no idea what's going on, but seems that my phone is doing worse and worse as time moves on. At least I can still boot into recovery and download mode, so (hopefully) something can still be done. As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Sirius8 said:
...
As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Click to expand...
Click to collapse
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
McXred said:
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Click to expand...
Click to collapse
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Thank you so much for the replies guys, I'm glad there's still hope for my trusty SIII.
Are there any alternatives for sammobile.com though, since it requires premium account for the firmware I need. I've found another mirror on the site mrcrab.net/stockrom/2444.html (mirror 1 leads to sammobile.com, while mirror 2 leads directly to rapidgator), but can I trust it not to mess my phone up further?
Try updato.com for the firmware.
Hawaiihemd said:
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
Click to expand...
Click to collapse
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Sirius8 said:
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Click to expand...
Click to collapse
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
McXred said:
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
Click to expand...
Click to collapse
Good idea. I would also keep it on the charger while booting.
This could be a symptom of a defective battery. So these steps might help.
Looks like you were right guys. I've recharged the battery and tried to flash the stock firmware again, but for some odd reason (it seems like I can't do the same thing twice with this phone ) Odin was giving me grief and couldn't establish proper connection with my phone, even though it recognized it at the beginning of the process. I've tried changing cables and ports, but with no avail.
After I gave that up, I tried booting the phone up anyway, but keeping it plugged in the charger this time. It booted right up, but I expected it to crash and reboot at any moment. So I sped up through the settings a and login processes, but it still worked like a charm. I've checked the camera and everything worked perfectly. So I kept it on charger for a couple of hours, to check if I would have any random crashes, but nothing happened. After I was sure it was stable, I unplugged the charger, and within the second I did that the phone crashed and got stuck in the bootloop again.
I've plugged the charger back in and it booted up just fine. The battery level was 89%, and I left it on charger the whole night (12+ hours). It had 90% when I woke up, it's back at 89% right now.
So, everything points to a faulty battery, but it seems strange to me this happened just as I was flashing another ROM, even though I never had any problems with it before. And even though it wouldn't let me boot, I could use recovery and download mode for as long as I liked, and once I did boot with the charger plugged in, the battery wasn't drained but it was around 90%.
Hawaiihemd said:
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Click to expand...
Click to collapse
Still on charger, still 90 percent.