Develop Bugs

Bricked Boot sequence

Fellow rooters and modders,
I have just done a serie of stupid things.
1) I have rooted my desire with the root sequence described from Modaco (risk free rooting. My phone was unlocked, so no need for the Goldcard.
2) Then, I installed clockword mod, and installed different custom roms (latest one was Defrost 1.8) from the rom manager.
3) As i was getting sick of the low on space notifications, I wanted to format my SD card through ROM manager, to support ap2sd . I highly suspect this was unnecessary. Anyway, after I launched this process, my device rebooted. I waited and waited. And finally got tired and interrupted the process by rebooting. I have not been able to start a single rom since.
I tried flashing, wiping and erasing everything I could (data, cache, dalvik, ST-ex, SD Card) and install new roms through clockword..
It still won't go past the green HTC screen, the screen stuck and lighting my face in despair...
What can I do to fix the boot sequence, and "start from scratch"'????
Any help would be appreciated, I am now down to make a Goldcard, even though I am convinced this won't help any....
Thanks in advance.

just remove the battery. put it back into the device. then make root again:
http://theunlockr.com/2010/06/07/how-to-root-the-htc-desire/
wipe erverything

chrysochire said:
Fellow rooters and modders,
I have just done a serie of stupid things.
1) I have rooted my desire with the root sequence described from Modaco (risk free rooting. My phone was unlocked, so no need for the Goldcard.
2) Then, I installed clockword mod, and installed different custom roms (latest one was Defrost 1.8) from the rom manager.
3) As i was getting sick of the low on space notifications, I wanted to format my SD card through ROM manager, to support ap2sd . I highly suspect this was unnecessary. Anyway, after I launched this process, my device rebooted. I waited and waited. And finally got tired and interrupted the process by rebooting. I have not been able to start a single rom since.
I tried flashing, wiping and erasing everything I could (data, cache, dalvik, ST-ex, SD Card) and install new roms through clockword..
It still won't go past the green HTC screen, the screen stuck and lighting my face in despair...
What can I do to fix the boot sequence, and "start from scratch"'????
Any help would be appreciated, I am now down to make a Goldcard, even though I am convinced this won't help any....
Thanks in advance.
Click to expand...
Click to collapse
Have you tried to reformat your sdcard ?

Answers
I tried to remove the Battery, Install a different SD Card, Format the SD Card I had, wiping everything (Factory Reset, Dalvik, etc.......).

I finally got past that screen, by actually, redoing the entire root process from Paul o Brien again.
But when I try to get back to shadowfrost 1.8, it stalls again at boot screen.... It might just be an issue with this particular rom...
Thanks for your help, I will try to post again on that thread...

[Q] [solved] Bootloops with every ROM except last nandroid backup

Hi,
I have a strange problem here:
My Desire keeps bootlooping with every ROM I flash, even if I flash the ROM thats currently running stable on my device for weeks now.
Its a T-MOB (debranded) wit HBOOT 0.80.0000 and AMOLED display.
I'm not using A2SD ROMs.
I can only recover the phone if I use my last nandroid backup.
I tried factory-reset from phone - bootloop. Wiping from recovery - bootloop.
Tried flashing some ROMs (including exactly the one I currently run) - bootloop.
The loop starts on the 2nd bootscreen (the animated one).
Any ideas would be helpful. I thought about applying a RUU - but if that causes a bootloop afterwards... there would be no way to recover from that I fear.

as stated in many posts, this is a sdcard problem.
formatt your card to fat32 and flash the rom. don't forget to backup important data.
Regards
Marios

Thanks for your reply mariosraptor - I did read several posts explaining that bootlooping is a sdcard issue - I reformatted the card but still get bootloops.
So I tried some different stuff - and successfully flashed several 2.1 images without getting bootloops.
Flashing any 2.2 ROM afterwards got me bootloops again, so I'm still not sure if my loops are caused by the corrupt sd.
Now I took my goldcard and flashed the stock 1.21.405.2 image (lost root during the process but thats no issue).
Do you think its safe to apply the 2.09.405.8 OTA my phone is offering now?
If its really the other sd that was causing the issues it should be safe...
Will I still be able to flash back to an old version with the goldcard (via PB99IMG.zip)?
I know that the OTA comes with a new HBOOT but I still can root it with Unrevoked afterwards. But I'm not sure if I can recover the phone if its looping after the OTA

Solved: replaced sdcard, rooted with Unrevoked, flashed 2.2 ROM - no more bootloops
Old sdcard -> trash (have been using it for almost 2 years, still from my HTC Magic)

happy you solved your prob.

CWM Recovery Reboots when wiping /data

I'm having a strange problem with my phone. Earlier today it stopped booting for some reason (Gets to boot animation, then reboots), so I figured something was wrong with my ROM. So, I went into CWM and tried to wipe my phone, but when it got to wiping /data, my phone rebooted. Nothing allows me to format /data, and my phone refuses to boot. I would Odin to stock, but I don't have the files (or know which ones to use as my phone had the bootloader required for newer CM), and I'm worried it may cause more problems. Anyone know how to fix this?
FIXED: So... Yeah, that was weird. The second (and I do repeat, second) time I tried to wipe data with no external sdcard (A suggestion I saw in another thread), data formatted like it was no one's business, and I was able to flash a new ROM to my phone. So, I guess everything is good now.

[Solved] Issues activating SGS3 SPH-L710 on Sprint with Custom ROM + lots of problems

Hello all!
This is my first foray into the world of custom Android systems, and I'm having a hell of a time with it... if somebody would be able to help me out, I would greatly appreciate it.
First off, the situation:
I am on Sprint, and I recently bought a Samsung Galaxy S3 (SPH-L710) from Sprint to use as a backup phone, I used it for a while on Stock, then deactivated it so I could give it to my wife. First though, I wanted to put a custom ROM on it, and experiment/play around a bit and see what this world of options could do for me. Long story short, I ended up flashing an AICP ROM, and everything seemed to go smoothly, but when I went to activate the phone on my account again and it would not work no matter what I tried (details below). I figured maybe I could activate on the stock setup then just restore my custom setup, so I tried to revert to my stock ROM backup and I couldn't do anything because I was constantly getting messages that various programs had closed... Then I tried to wipe and restore my custom ROM backup and I get stuck in a boot loop... so I tried to flash a stock recovery and I get stuck in a boot loop... I'm out of ideas here, and now I'm stuck with a phone I can't use or do anything with, and I can't activate.
Details:
The initial rooting/install process seemed to work ok, and was fairly straightforward. I followed various guides on http://galaxys3root.com/ to get my phone rooted and backed up (Don't recall which ones now, but I've read through so much by now I don't know if it matters...).
My phone:
Samsung Galaxy S3 (Sprint) SPH-L710
Modem: L710SPRDNJ2
My Desktop:
Debian Linux
Here's the steps I performed:
Rebooted phone in Odin mode
Downloaded CWM S3 Sprint Recovery from the http://galaxys3root.com/ website (can't find the link any more)
Flashed the CWM recovery using Heimdall then rebooted phone into CWM
Installed SuperSU through CWM, then rebooted
Checked that the phone was rooted successfully (it was), then ran Titanium Backup on the whole device to my SD card, then copied the backup files to my desktop computer
Rebooted into CWM, and performed a backup through CWM, then rebooted and copied the CWM backup to my desktop.
Downloaded AICP Rom for my phone from here: http://downloadandroidrom.com/file/GalaxyS3Sprint/roms/AICP/aicp_d2spr_lp-10.0-RELEASE-20150707.zip, put it on my SD card, then installed it through CWM and rebooted
At this point, I was happy with how everything was working, so I did some minor theme customizations then made another backup through CWM, and copied it to my computer, but I did NOT run Titanium this time...
After all of this, I tried to go ahead and activate it through the Sprint web service. This process failed continuously with an unhelpful error message of "Sorry, this device can't be activated right now". I then got on Chat to see if they could activate it manually, and then the problems began. They did their thing activating the phone, but when I booted up I got no data connectivity, and couldn't make calls, and the SIM was not changing over to the new number. I was on the chat with them for over an hour trying to get the situation resolved, but that finally ended when they started asking me to punch in ## codes, because I discovered that none of them worked on my custom ROM. Some quick research told me that this was non-trivial to get around so I had them switch everything back and I started researching the issue.
I found this thread: http://forum.xda-developers.com/showthread.php?t=1626638&highlight=sph-l710 that looked like it would let me do what I needed from the custom ROM, but I couldn't tell if it would fix my problem for sure, so I figured "I'll just restore my stock setup from that backup I took, activate it and update, then start over". This is when things got really frustrating...
First I rebooted into CWM, went to 'backup/restore', and restored my stock backup
Rebooted, and as soon as I got past the lock screen, I get inundated with messages of various apps being closed unexpectedly.
I researched a bit, discovered the issue may be caused by stale dalvik cache, so I rebooted into CWM, cleared the dalvik cache, formatted the /cache partition, then tried to restore the stock backup again, but this time I get stuck in a boot loop.
I then rebooted into CWM, tried to restore the backup of my AICP ROM, only to be stuck in a boot loop as well.
Trying to get into any usable system, I rebooted to CWM, cleared dalvik cache, then formatted /cache, /data, and /system just to be sure, and re-flashed the base AICP ROM I started with. This worked fine, and before long I had stock AICP back
Since I still couldn't get the phone to activate in the custom ROM, and my backups are apparently completely useless, I rebooted into CWM, wiped dalvik, /cache, /data, and /system again and tried to install a different stock ROM I found in the XDA forums (here: http://forum.xda-developers.com/galaxy-s3-sprint/development/stock-rom-4-4-2-t3010642) only to be greeted by another bootloop
At this point I've spent well over 24 man-hours trying to get this to work, reading, researching, flashing, etc all to no avail. Nothing I do seems to work, and it seems like every article, tutorial, or forum thread I read either has nothing to do with my device, is too old, or doesn't describe my problem.
I'm at wits end, and am so frustrated I'm ready to just give up and smash this device and buy a new one... My questions to the community are as follows:
I know I screwed up on a couple of things, but in my initial research of doing this there was no indication that these were even things I needed to watch out for... Is there any more organized sources of information for doing this sort of thing?
Does anybody else out there use Sprint on a custom ROM, and if so how you you pull this off
Where else have I screwed up, and how can I fix this situation? (My end goal is still to get the S3 onto Sprint with a custom ROM)
What can I do differently next time? I would like to figure this out and do it to other phones and devices I have, but if it's this much trouble every time, I just don't have the time to mess with it.
Thank you in advance, and I appreciate any information that the community can provide.

This sounds like a CWM problem to me. If I were you, I'd boot the phone into Odin Mode and flash TWRP ( www.twrp.me ) then try flashing the latest aicp nightly downloaded from the official site ( www.aicp-rom.com ). Check the md5sums on everything! Then maybe try flashing a touchwiz ROM and activating your phone. Remember that you need to wipe the internal storage when you go between KitKat and lollipop.

I'm fairly certain you have to do activation with the stock Touchwiz roms -- once the phone is activated you can flash a custom.
You should go into recovery and wipe everything (System/data/etc) EXCEPT for the External SD Card
Power off - pull the battery for a few - power on directly into download mode
Odin NJ2 back onto the phone and reboot and activate it (skip through most of the setup since you'll flash a custom after)
Once you know it's activated and working under the stock Touchwiz, then again power off and Odin TWRP recovery
Then you can go back into recovery, wipe everything except External SD, and flash the custom rom back on.

Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!

afarris01 said:
Looks like swapping CWM for TWRP did the trick.
Flashed TWRP no problems, and put CleanBean on there to get the phone activated. Still wouldn't work automatically over the Sprint website, but I got on chat with them and they fixed me right up. Downloading a fresh copy of AICP now...
Is it worth it to keep the CWM backups I made earlier, or should I just go ahead and flush them? I figured just get rid of them since restoring them wasn't working anyway, but I figured I would ask.
Now to move all the data over to the new phone. Thanks so much for your help guys!
Click to expand...
Click to collapse
Get rid of them. TWRP can't restore CWM even if the backup is good

Bootloop at green HTC Boot Animation after trying to restore TWRP

Hello,
sorry if this has been mentioned anywhere before, but I wasn't able to find something similar.
So I know why way around with my old Nexus 5 in things backing up the phone with Titanium or TWRP, but since it's wifi module died on me I switchted to the HTC 10, which is kinda intimidating to me when it comes to updating to new OS or backing up. With the NExus 5 it was a walk in the park for me.
First, I don't really understand the concept of S-On and S-Off. Don't know if this is related to my problem, just wanted to mention it.
My HTC 10 is rooted, bootloader unlocked, S-On and runs on 7.0 2.41.401.41.
TWRP is the latest available version.
Before I rooted the phone I made a backup of the stock system image etc like explained in one of those "how to root the htc 10" tutorials (no writing allowed).
To root I had to allow writing onto the system partition of course.
Now, I made an TWRP backup. I backed up everything that was available in TWRP. Userdata, cache, system etc.
Few weeks ago I ran into some problems (I though I did, turned out Google App is just weird) and wanted to restore my TWRP backup.
So I did. Went to TWRP and restored the backup from my SD card.
Got no error messages during the process, but when I wanted to boot up the phone the green HTC boot animation did its thing and then froze at the HTC logo, which would result in a bootloop after ~10 minutes of waiting.
Could force the phone to go into bootloader and from there into TWRP, but that's the best I could do.
Also removed SD and SIM card trays, but that didnt do anything.
Had to factory reset and then do a backup via Titanium backup, which is better than nothing but still a pain in the a** because some things just have to be set up manually, which took me quite a while. I honestly don't want do that again anytime soon
Does anyone have an idea what could went wrong or what I did wrong during the backing up and restoring process?
Except for that, I tried to understand how to update to an upcoming version of the OS when the phone is rooted with S-On and how I could keep my userdata? On the Nexus 5 I just manually installed everything via adb except userdata.img and only had to re-root the phone afterwards. I am afraid this isn't possible with the HTC 10, am I right?

The HTC 10 forces encryption and that has broken TWRP restore for me if I try to switch between ROMs. If I switch ROMs then I have to do a full wipe / format. The one time I tried to go back to my original OS I had a similar issue and I ended up flashing the full RUU to get back to stock.
The only time I am able to restore in TWRP is if I'm returning to the same ROM that I am currently running. Even then I usually just restore the data.