While I was attempting to flash CM 13.1 to the phone, it got stuck in a bootloop. Would not get past the white startup/splash screen. So, I booted it into TWRP and attempted to install the recovery I had made using TWRP. It ended up throwing me an error (I don't remember the code.) Anyways, I got the bright idea to completely wipe my phone and retry it. Now TWRP deleted my recovery, and my OS is gone. It was rooted and had SuperSU installed before it got bricked. Any help at all?
Regards,
Cheer
Hi Cheerfulfilms
Next time when you brick your phone, read this thread. I hope you'll be good now.
Cheers
bemolx said:
Hi Cheerfulfilms
Next time when you brick your phone, read this thread. I hope you'll be good now.
Cheers
Click to expand...
Click to collapse
The Xtreme System ZIP is no longer available.
*update*
I decided to try my own way and it worked very well. Using TWRP I was able to transfer a ROM onto a MicroSD, and then install that ROM from TWRP. It's a lot less complicated than the thread given. The Xtreme stock ROM is running very well though.
Related
I think I screwed the pooch. I finally took the plunge and Rooted/S-off (with Sunshine) and installed a custom recovery. Issue is, I think I had TWRP installed and then installed Philz_touch_6.43.6-m8. Now, I can't get out of a recovery boot loop. I'm not 100% sure how I managed this but now when I reboot, I'm getting the red text at the bottom stating "this build is for android development purposes only" and boots me into TWRP. If I try to fastboot flash recovery and install the Philz recovery again, it does it's business, boots into Philz and when I go to reboot Philz it reboots into TWRP. Am I hosed? Any help is greatly appreciated. I was hoping by reflashing Philz it would remove the ability to boot into TWRP. This sucks!
Thanks in advance.
I actually just think somehow I hosed the system. I was able to download a custom ROM and get out of this boot loop hell!
upnsmoke67 said:
I actually just think somehow I hosed the system. I was able to download a custom ROM and get out of this boot loop hell!
Click to expand...
Click to collapse
You probably installed twrp into the stock partition, glad you got it fixed.
upnsmoke67 said:
I actually just think somehow I hosed the system. I was able to download a custom ROM and get out of this boot loop hell!
Click to expand...
Click to collapse
I know you fix it...but did you 1st flash twrp via the terminal emulator?
Thanks for the reply guys and sorry I didn't answer sooner. I'm not 100% sure how I did it honestly. First time with an HTC coming off Samsungs.... everything is humming along beautifully and I'm digging the stuff I'm learning from here about these powerful devices. I'm a flashing fool!
upnsmoke67 said:
Thanks for the reply guys and sorry I didn't answer sooner. I'm not 100% sure how I did it honestly. First time with an HTC coming off Samsungs.... everything is humming along beautifully and I'm digging the stuff I'm learning from here about these powerful devices. I'm a flashing fool!
Click to expand...
Click to collapse
I asked bout terminal emulator because twrp has the partitions mapped wrong. So if you do that it will flash to the system one which is what sounded like you did.....I been with HTC forever just a quick tip always fastboot flash if you can as it is the safe way..never use apps or emulator to flash...
OK cool Tigerstown... many thanks for the tip!
I can't change my current ROM, I'm running Baked with Android 4.2.2, I had TWRP 2.7.0.0 and now I upgraded to 2.8.0.1 with the same results.
I've tried with several ROMS, I do the steps for each rom carefully, making a backup before doing a full wipe, etc, and after the install, when I reboot, I get stucked on the loading screen, I don't even see the custom ROM logo, just the Asus logo.
After the boot loop, I enter again in recovery and recover the Baked backup, and it works again.
I'm really desperate because the Baked ROM don't run well, is very slugish, so for me an upgrade is mandatory.
I've tried with several custom ROMs, the last one I tried was KatKiss Lollipop.
Any help would be greatly appretiated
krusty_da said:
I can't change my current ROM, I'm running Baked with Android 4.2.2, I had TWRP 2.7.0.0 and now I upgraded to 2.8.0.1 with the same results.
I've tried with several ROMS, I do the steps for each rom carefully, making a backup before doing a full wipe, etc, and after the install, when I reboot, I get stucked on the loading screen, I don't even see the custom ROM logo, just the Asus logo.
After the boot loop, I enter again in recovery and recover the Baked backup, and it works again.
I'm really desperate because the Baked ROM don't run well, is very slugish, so for me an upgrade is mandatory.
I've tried with several custom ROMs, the last one I tried was KatKiss Lollipop.
Any help would be greatly appretiated
Click to expand...
Click to collapse
What is your bootloader version ?
Are you doing a full wipe before installing ?
Thx Josh
If you can adb to it then go for a full wipe and try...same thing happened to me going from stock 4.2 to katkiss 4.4.4..
Look for the post i just did in tims thread for 4.4.4.. its got the links to the post...
Remember. ..wipe 'misc' as it seems gremlins like to hide in there..
Worked for me...
lj50036 said:
What is your bootloader version ?
Are you doing a full wipe before installing ?
Thx Josh
Click to expand...
Click to collapse
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
dgcruzing said:
If you can adb to it then go for a full wipe and try...same thing happened to me going from stock 4.2 to katkiss 4.4.4..
Look for the post i just did in tims thread for 4.4.4.. its got the links to the post...
Remember. ..wipe 'misc' as it seems gremlins like to hide in there..
Worked for me...
Click to expand...
Click to collapse
I installed ADB on my pc (win8 x64), and started to do the blob backup mentioned on the first link in your other post, followed all the instrucions, after the "Step 1" in the "Wheelie" menú, the tablet shuts of, as it should, but when I turn it on again, it no longer boots into android, it gets stuck in a boot loop, now I don't have TWRP anymore, I have the FlatLine CWM, so I can't recover the image created with TWRP, so I'm stuck with recovery,
I'm still trying to fix it, I'll try to revert to stock and start from there.
Thanks to the both of you, wish me luck!
krusty_da said:
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
Thanks to the both of you, wish me luck!
Click to expand...
Click to collapse
That is the issue mate you need to be on the bootloader ending with 27.5 ....... :good:
Let me know if you need any help making that happen .....
Thx Josh
krusty_da said:
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
I installed ADB on my pc (win8 x64), and started to do the blob backup mentioned on the first link in your other post, followed all the instrucions, after the "Step 1" in the "Wheelie" menú, the tablet shuts of, as it should, but when I turn it on again, it no longer boots into android, it gets stuck in a boot loop, now I don't have TWRP anymore, I have the FlatLine CWM, so I can't recover the image created with TWRP, so I'm stuck with recovery,
I'm still trying to fix it, I'll try to revert to stock and start from there.
Thanks to the both of you, wish me luck!
Click to expand...
Click to collapse
Yes, dont worry too much as I was in the same boat.. lost the recovery a few times.. and or couldn't get recovery to mount any partitions..
If you have still got ADB connection then use Busters wipe... multiple times.. as it cleaned mine out..
Then I used the easyflasher to flash the CWM kitkat Version and used this to flash Tims Kitkat off the external SDcard..
booted in to Kitkat with out loading Gapps.. let it settle then booted in to the recovery then booted to Bootloader..
and reflashed TWRP 2.8.. flashed Gapps with this and its all settled in..
One thing that I made sure off was to boot the device after flashing a recovery.. somewhere in all the instructions it says to to this.. So I made sure I did it..
otherwise I kept getting that password screen in TWRP...and if i got that then I knew it was not mounting anything..
K.. keep at it.. if there is will there is a way and as said if you have an unlocked bootloader and ADB you are half way there already..
Good luck..
lj50036 said:
That is the issue mate you need to be on the bootloader ending with 27.5 ....... :good:
Let me know if you need any help making that happen .....
Thx Josh
Click to expand...
Click to collapse
Thanks! I'm loading Lollipop for the fisrt time now!
I found a tutorial here to change the bootloader:
http://forum.xda-developers.com/showthread.php?t=2187982
And downloaded the latest firmware from here:
http://www.service.asus.com/#!downloads/c1wax
Thanks again
Hello XDA Forums.
Well, I'm pretty new to rooting. So, I rooted my Moto G 2014 model yesterday, and everything went smoothly. I accidentally installed TWRP 2.7 on my phone and didn't realize it until now. So, I went forward and thought about installing CyanogenMod, but before, I made a backup using TWRP. I had around 35% battery when I started. The backup was successful, but when I booted my phone, it didn't boot. First, I got an Android is starting followed by the screen turning black and back to the Android is starting. I rebooted my device, and then all I got was a black screen. Apparently, my TWRP doesn't load either, I get weird lines all around the screen and stuff. Although sometimes it would load, but I don't know what to do.
I'd be extremely happy if someone could help me. I've already tried searching for similar cases but found none.
Edit:- Solved it! Had to make flash CWM, and manually install another OS. I installed Cyanogenmod. The recovery mode is adb in itself, so you just use the adb push commands to copy the ROM and flash it from Recovery.
Alexander_the_B0ss said:
Even though i don't have any experience with Motorola devices, you might want to restore it to stock and reroot and install the latest TWRP version available for your device. Your device has a subforum, so you have a better chance to look there for instructions.
Click to expand...
Click to collapse
Thanks for replying! I'll take a look there!
YatharthRai said:
Edit:- Solved it! Had to make flash CWM, and manually install another OS. I installed Cyanogenmod. The recovery mode is adb in itself, so you just use the adb push commands to copy the ROM and flash it from Recovery.
Click to expand...
Click to collapse
Good news
Thread closed
my phone just suddenly got stuck on boot
i rooted it a few months ago, though never really messed up with anything.
anyway, i dont if whatever i am doing is right, but i'm trying to install the stock recovery
and since i am in twrp, i cant really install it, reading error.
how can i remove twrp so i can install the stock rom?
dansama007 said:
my phone just suddenly got stuck on boot
i rooted it a few months ago, though never really messed up with anything.
anyway, i dont if whatever i am doing is right, but i'm trying to install the stock recovery
and since i am in twrp, i cant really install it, reading error.
how can i remove twrp so i can install the stock rom?
Click to expand...
Click to collapse
Greetings and welcome to assist. The easiest way to install stock recovery is to reinstall a stock rom but twrp won't be causing your bootloop. I would try doing a factory reset first and if that doesn't work reflash a rom through twrp
Good Luck
Sawdoctor
Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?
TWRP is a recovery. A bootloader is a bootloader.
This is covered in every rom thread that updated from L to M.
lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?
Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please