Yeah, i finally made it. I bought a TMO-DE One S (With S4 Processor) 5 Days ago, unlocked the Bootloader (HBoot 1.09), rooted and SuperCID´d it, installed CWM Touch and installed TrickDriod V8.0 incl. its Tweak Package. After that i installed another Radio and everything was fine. It could have been SO easy, but i just HAD to do more, and now its soft-bricked.
At all TrickDroid is a really good ROM, but i hated the thingy that it shows G symbol instead of H when getting HSPA speeds. So i decided to dump it and go for a 4.0.4 / Sense 4.1 Stock Rom without branding instead until a JB / Sense Rom comes out. And thats were the trouble started. i flashed the stock rom with CWM, installed the boot.img that came shipped with it and booted it up. I did a full wipe before flashing. It booted up, Sense Stock Background Image came on and it showed "Unfortunately Wiper App is closed" at the "Preparing phone storage" stage. After OK´ing that another Screen came up about some system service wouldnt respond (dont know the exact Text anymore) wich i could close or wait for it. No matter what i do, or if i do nothing, after ~20 seconds the phone crashes and restarts. After the first restart the phone only boots into a black screen but with the Android bar at the top is working with time, battery-charging and a warning smybol. But the Phone wont react to anything i do except for lockscreen button. When its "online" i can push files via adb to the internal SDCard so i thought it wouldnt be a big problem. i pushed ONE MaximuS V2.5 ROM to the SD Card, booted into CWM and installed it. then flashed the boot.img of it via fastboot and booted it up. but nothing happens. still black screen with bar on top and not reacting phone that reboots every 20 seconds. i allready tried full wipe, cache wipe, dalvik cache wipe and i dont really know what to do now.
A broken SD Partion cant be since i can push files via ADB to it and install them with CWM. But whatever i try to install every ROM boots only in this blackscreen. its clearly not hanging in bootloader, but in android itself. I dont really know what to do, and returning to my dealer is no option since Rooting, SuperCID´ing and flashing another ROM. You maybe have a Idea what to do now?
Peace
TK
PS: Sorry for my bad english, hope you can understand it
Edit: Okey, i got something. i formatted everything i could in CWM, and now (as its now supposed) it hangs in bootloader since no system is there for booting. The good thing is in CWM i get ADB Connection so i can still push files to the SDCard. Im now trying installing a ROM again. So at least i have a starting Point if it fails again
Edit 2: Okey, found it. The "Stock" ROM is broken, not my Phones Fault. and MaximuS just doesnt install right so nothing was changed. Installed TrickDroid again for testing and everything is fine again. Close this one...
Hello, I just flashed cm9 for my htc sensation. I booted it up and it goes as far as google sign-in. I choose what language id like and then press next. It starts loading and then crashes and starts booting up again and keeps doing the same thing over and over again. I've tried reflashing the ROM a couple of times. Also tried wiping cache, delvik cache, factory reset, pretty much everything i've seen people say on threads so far. Also, this same thing happened to me before I flashed CM9. I first flashed AOKP's Jellybean and this same thing happened. I scratched that ROM and tried CM9, hoping that I'd ditch the problem. Well here I am now with the same problem and without a phone. Any help would be much appreciated! thanks!
I attached a few images of the process, maybe itll help.
I'm just gunna give you the whole story.
I'm using TWRP Recovery.
I'm coming back to my d2vzw after a couple weeks of not using it (I got a different phone through work). I'm now back to using my GS3. I decided to update to the latest ROM version. I installed the slimROM stable that was just released, it was slow and they animations were choppy (which is really weird for slim). So I decided to try a different ROM. I've used carbon before, and I really like active display and HALO, so I decided to install that. It installed just fine, installed all my apps, rebooted. It froze on the initial splash screen, didn't even get to the boot animation. So I figured it was just a bad install, so I formatted and flashed from my external SD. Again, first boot just fine, then froze on second boot. So I put a https://plus.google.com/+AlexKruger/posts/dJGXsrAZvj4 in the ROM's community. They suggested that it might be a bug from installing it from my external. So I formatted, then moved the files over to internal, and flashed again. It booted fine, I got to the home screen and restarted before I did anything else. Froze, again. Then someone suggested, that I format, install it, boot all the way, reboot into recovery, wipe cache/dalvik and dirty flash from internal storage. Did it, froze on reboot. So I formatted one more time, and went to boot into recovery while figured out what to do, I accidentally booted into the system. It booted just fine, I went through the set up and activation screens, and it worked. So I rebooted, froze. Then someone suggested I switch recoveries, so I installed the latest CWM recovery, and tried everything all over again, still freezes on reboot.
I know I could just use a different ROM, but it's gotten to the point that I need to fix it. I want to get it to work because F*** you.
Please any help would be appreciated. Thank you.
Soooo. The photon i've been using since june lost it's identity (IMEI, ESN, MEID, etc. all GONE and DFS tool kept throwing nasty errors every time it tried to read or write to the phone) so i swapped the board out of my other photon with a broken screen into the pristine chassis of the amnesiac phone.
now the fun starts: i RSD back to stock to activate the phone, all's good while i'm on stock. but if i flash a rom like skrillax's CM 10.2, the phone will boot fine the first time, then upon reboot will hang at the unlocked bootloader warning screen. restoring a backup of stock fixes this issue, but i'd really love to have my CM back
Any ideas?
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
angahith said:
Weird
I had that once, during my endeavors. After wiping cache and dalvik again, it finally booted after like 5 minutes, though (never had anything take that long to rebuild the dalvik, though)
...but I assume you tried that already. Hrm.
Click to expand...
Click to collapse
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
solitarywarrior1 said:
well, i wiped everything (system, data, cache, and dalvik) like 4 times and flashed again. It did hang on reboot again, but i wiped cache and dalvik 3 more times and it's working great now!.
Thanks for the advice!
Click to expand...
Click to collapse
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
solitarywarrior1 said:
Update: it still seems to have issues rebooting without clearing caches, but shutting it down and cold-booting works perfectly.
Click to expand...
Click to collapse
I just ran into this issue too, after flashing CM10.2.
I can't boot any ROM right now. The phone always shows the unlocked bootloader screen and returns (without button press) to the recovery..
I will try flashing the stock FW with RSD Lite.
I have just been searching for a reason for this issue also.
I was running stock jelly bean, unlocked, twrp. Flashed CM 10.2, and it runs fine right until I reboot the device then it hangs at the red Motorola symbol. I have to hold the power button until it starts vibrating to shut it off. If I boot into recovery and do a factory reset it will then boot again.
I have tried updating to the latest version of TWRP (from 2.5), and tried both Milestone and Nightly versions of CM. I have flashed this phone at least 20 times today. Issue persists with or without Gapps.
I REALLY don't want to go back to stock after all this time I've spent, any ideas on what is causing this?
i had a similar problem monthes ago. i was able to boot but its not a fix more a workaround.
go to bootloader menu (Power+Vol-Up+Vol-Down)
and try the first option it called "normal powerup"
if it not work go again to bootloader menu and try "BP Tool"
same problem here...
after flashing cyanogenmod 10.2 and the first reboot the phone hangs
i restored original moto 4.1.2 from nandroid and now phone runs without problems. is there a problem with cm 10.2 ?
i used last night 20131127 gsm and swapped bootloaderimage.
Know this is an old thread, but after Motorola recently announced that they won't be bringing KitKat to the Photon Q, I finally decided to root and flash mine.
Can't begin to say how disappointed I am at Motorola on this one - the MSM8960 is well supported by KitKat and there are no technical reasons not to... at least Motorola is tactily admitting this is a penny-pinching business decision.
Anyways, I'm stuck at the same hang. Tried flashing known-good Photon Q builds and using the latest TWRP.
It took three flashes just to get the latest stable TWRP for it to take. I suspect the "JBBL" (Motorola Jelly Bean-era Boot Loader) is at fault here. CM just committed some patches to (in the near future) resume issuing builds for JBBL devices, but that won't fix the underlying problems.
And, since Motorola is abandoning the device, it looks like those won't get fixed either.
My next step is to restore via RSDLite, update PRL, Firmware, and Profile in stock ROM, and then start over. Disturbing that's needed, but now Motorola is Lenovo's problem I guess.
How long did you let it boot? Out of five XT897's I've owned, one woul ALWAYS take 15-60 minutes after an initial flash. I guess something was wrong with the memory. After an RSD-return-to-stock and back to CM it would take at least an hour to boot (repair process in the back during bootloader-logo). A wipe (internal too) and CM and it would take 10-15 minutes to get past bootloader logo.
Yesterday I restored a nandroid, wouldn't boot. Installed via zip and 15 minutes later it did boot again.
So just maybe you also have one of those special Photon's . It's worth a try.
I used TWRP 2.7.1.1 and M8 Snapshot in case you were wondering.
Hello everyone,
Yesterday I was using my TF101 and decided to reboot since it has been a while. Now, the TF101 doesn't want get past the "eee pad" screen and just constantly reboots itself without even trying to access the rom.
I went into TWRP and flashed my rom again, same results. Went back into TWRP and did a full restore, same results. The TF101 doesn't want to get past the initial boot screen.
I have a feeling the hard drive went out? Any idea what tio try next? The only thing I did before the reboot was install eBay app.
Tried wiping absolutely everything in TWRP and flashing the ROM again ?
Bootloops can be caused by apps on the DATA partition too
Try flashing TWRP again too
Wiped everything I could. Installed KitKat, all good now. Thanks!
Cool :good: