Hi All,
My phone decided to put itself into an infinite reboot loop today for no reason. It was running Android Revolution HD 31 fine before this point (S-On).
I could not get it to start so I wiped in recover and tried re-flashing, and it rebooted during flashing
I have tried uploading smaller roms to it, but it reboots during the adb sideload or adb push, so currently I am stuck, I also download the RRU but it does not detect my phone
Any help would be much appreciated!
Update it finally flashed everything is crashing will try a wipe and flash again.....
make sure it is charged before flashing, at least 30%.
never change a rom without a full wipe.
Related
Hello everyone,
I just hardbricked my SGS+ and now I'm a bit curious how this could happen.
This is what I did:
I used to run CM9 RC5 from arco68 along with the Kernel for ICS from Christopher83 and CWM 6.0.1.2.
Because my phone always lost the wifi-connection and also had some freezes I decided to try out CM10 Beta 3 from ivendor.
I backuped my phone, downloaded the zips and even verified the MD5sums. Next I flashed CWM 6.0.1.9 as recommended in the thread from ivendor.
After exporting the nandroid backup and other stuff like photos to my computer I wiped everything as mentioned in the thread, flashed the two zips and rebooted. Everything went fine and I was almost ready with setting up my phone again when I got my first softreboot.
Suddenly it showed the CM-bootlogo and after maybe 10 seconds I was back on my homescreen. I got another two or three softreboots until I decided to flash the Kernel 3.x from CastagnaIT.
I rebooted into recovery, wiped cache and dalvik cache, flashed the zip and rebooted.
Now I wanted to reboot into recovery again to fix permissions but instead I got a softreboot and my phone stuck at the CM10 bootlogo.
I waited for around 5 minutes and then I just turned the phone off and booted into the recovery mode.
Because I wanted a clean install without any problems like softreboots I decided to wipe my phone again (data, cache, system) and just reflash the zip for CM10. And at this point everything went wrong.
I flashed CM10 but when I tried to flash gapps my phone just turned off. And no, the battery was not empty. In fact the battery was at around 50-60% and my phone was also connected to my computer.
I tried to turn on my phone but now it stuck at the Samsung bootlogo.
The next thing I did was probably a horrible mistake. I tried to un-brick my phone but I did not realize that I could boot into download mode without problems so I guess my phone wasn't softbricked at all.
Well, after that I still stuck at the Samsung bootlogo and couldn't enter recovery mode. I got into download mode somehow and maybe this was my second mistake. I tried to flash the "i9001Reset.zip" via Odin. Everything went fine but when Odin said "Close serial port and wait until rebooting" my phone was completely dead. I think it was while I tried to flash the reset-file when I got a message like "MBR: read failed". So somehow I managed to destroy my master boot record.
Now I can't turn on my phone or enter download nor recovery mode. I already removed the battery for about 45 minutes but this didn't work either.
My phone is dead but at least I saved the important data and maybe I'll get a new one through warranty. Or I just buy a Nexus 4.
My questions are:
What did I do wrong especially when I tried to save my phone?
How can I prevent such things from happening?
And at which point I should have got help here in the forum or elsewhere?
I would really appreciate some tips for the future because I already flashed and used a lot of different ROMs but this is the first time something really went wrong.
Thanks for reading and thanks for your help in advance.
(Please excuse my non-perfect englisch.)
Greetings,
Mangoniter
Hi Guys,
So i've been away from flashing ROMs for awhile but have been playing with my HTC one and have had no issues until today.
I downloaded the new ARHD, put it on my SD card and went to install it. Aroma played nice for once but as soon as it started installing and doing the full wipe the phone rebooted. So i tried again with the same result. In the end i passed by the full wipe option and managed to get to the final step of rebooting and then it would freeze which it did 3 times.
Now i can see the ROM but i can't mount the SD card in CWM to put anything else on there so my phone is useless. I am not really experienced with ADB having only used it briefly with my sensation a few years back.
Can anyone help?
Thanks in advance
connect phone to comp, open cmd in folder that you have rom on computer (cd/location/here/rom.zip) then do (as long as you set up adb correctly) adb push rom.zip while selecting flash rom from sideload. cwm will do the rest.
I think all that happened was Aroma crashing every time. Correct me if I'm wrong but that's what it sounds like to me.
Hi,
I cannot get the phone recognized in fastboot, if i let the phone start to boot i can see my device.
Sorry if this isn't clear
Glenn.Bre said:
Hi Guys,
So i've been away from flashing ROMs for awhile but have been playing with my HTC one and have had no issues until today.
I downloaded the new ARHD, put it on my SD card and went to install it. Aroma played nice for once but as soon as it started installing and doing the full wipe the phone rebooted. So i tried again with the same result. In the end i passed by the full wipe option and managed to get to the final step of rebooting and then it would freeze which it did 3 times.
Now i can see the ROM but i can't mount the SD card in CWM to put anything else on there so my phone is useless. I am not really experienced with ADB having only used it briefly with my sensation a few years back.
Can anyone help?
Thanks in advance
Click to expand...
Click to collapse
If it got all the way to the "Reboot Phone" stage--meaning that the phone wiped and installed the new OS--you should be fine to boot the phone up normally. I'm sure you have, but have you tried just powering it up and seeing if it'll load into Android? Reminder: First boot after a new ROM always takes a few minutes.
Hey guys,
So i ended up continuing to flash it trying various options and eventually it came up ok... The scary thing was the random reboots during install whilst aroma was trying to wipe everything...
But all sorted, thanks everyone!
UPDATE: LOOKS LIKE RUU FIXED IT.
==============================
I bought this phone last night. Already having major issues.
Unlocked and flashed clockwork. Rooted and worked well.
Then I accidentally tried to flash a GSM rom which caused phone to start booting, showing blinkfeed while not connecting radio, then rebooting about about 40 seconds.
I immediately tried to restore the backup, but even the reflashed stock backup was not connecting, then rebooting.
I have since reflashed recovery a countless times via adb, cleared cache repeatedly, flashed several different M7WLS stock-flavored roms, including regular oem stock. I have tried using adb with the stock boot.img, stock recovery, various adb sideloads, and have even tried using TWRP to flash a couple different stock roms. Even worse, at some point the "sdcard" was wiped and I no longer have the original backup (but it didn't work anyway). After all of this flashing it's still doing the same thing, except now it's not showing blinkfeed, just a statusbar and a black screen. Trying RUU now.
Why is it still boot looping on me? I've never had this much trouble with any of my phones.
If I'm unable to get this working, what do I do? Contact HTC or Sprint? What am I going to have to pay?
So today I was preparing to flash another ROM, so I connected my phone that was on a Sense ROM (OMJs v1.8) and began to delete folders on the phone from my computer. Once I did that I copy and pasted the latest gapps and CM nightly onto the root of my phone. All of a sudden my phone rebooted and would not stop, right in the middle of the file transfer. I did not flash this rom after it copied because the phone began to reboot mid-paste. However, I had recently just installed philztouch custom recovery so I thought that the recovery was the problem. I then installed TWRP through fastboot. Keep in mind I couldn't even access my recovery. Everytime I tried, the recovery screen would show up for a second and reboot. No matter which recovery I tried, my phone could not reboot recovery. So here I had a phone that still has my OS installed and in tact..but for some reason randomly rebooted out of nowhere, continued to reboot over and over again, couldnt even boot recovery or the actual OS. I had no idea what the problem was. When I finally calmed down and got recovery to boot philz touch, every time I tried to perform a simple wipe, the phone would stop mid wipe and reboot. Luckily I got recovery to consistently reboot and I finally got a ROM to install through recovery (not adb sideload). My question is has anyone else experienced this? And does anyone know why this happened?
Sent from my One using XDA Premium 4 mobile app
Hello all. I have been in the Android root community for a little over three years, and even after tinkering with the various devices I've owned since, I cannot get my T599N to come out of its current bootloop.
A background: I had been checking some things in my settings app (running stock, rooted), and I ended up just force closing the settings app to get out of it quickly. Well, this action deleted all of my text messages, and later on it removed my notification bar and made my wallpaper go black. I ended up booting into recovery mode to try and clear the cache. After it cleared, I rebooted, and bam, the bootloop started.
Now, here's what's interesting. The phone is in a bootloop where it displays the first boot message (SGHT599N Galaxy Exhibit or whatever), and then it tries to boot into cwm recovery, displays the loading screen for that for 2 seconds, and just reboots again. I've tried installing a stock rom from ODIN with no success. The rom apparently loads onto the device but it's still in the bootloop. After this, I tried to install philz recovery to try to install a zipped rom to get the device to somehow boot. I tried to factory reset it for installing purposes, and it just reboots. The device will literally clear everything but /data, so that makes me think that it may be a file system problem. I really need to get it to work, as I am out of a phone right now.
Does anyone have any suggestions? I've tried everything I know.