Here's the background story. I had been running Team EOS 4 for quite some time with no problems at all. I decided to encrypt my device. After encryption an update for the Team EOS rom became available and I went to flash it only to find out I could not get into TWRP recovery console. I was running twrp 2.5 and decided to try an earlier version, so I hooked up the Xoom and fastboot flashed an older version. I was able to get into twrp recovery using version 2.4.4, but it would not mount /data. With great help from the TWRP team, I was able to get /data mounted and was able to perform a factory reset to remove the encryption. I then flashed the latest version of twrp, 2.6, and installed the latest Team EOS rom. I then rebooted, but I can not get past the Motorola splash screen. I let it sit at that screen for 2 hours before I went to bed and when I woke up, the battery had died, so I'm assuming it never booted. During the 2 hours I was up, I tried to get into adb, but it told me the device was offline. Is there any way to fix this or did I just make myself a brand new paperweight? I am kind of a noob when it comes to the android stuff. Thanks in advance.
Edit-
Nevermind. I broke the cardinal rule of not reading other threads before posting. There was something wrong with the latest version of the Team EOS rom and once I want 2 versions back, it booted up. Sorry for the post. This thread can be deleted.
Related
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
netwokz said:
If you look through the last few pages of the Playground ICS thread, it is an issue and can be fixed, but its not that easy unless you know what you are doing. I hope you have a linux box.
Look at these posts for help.
http://forum.xda-developers.com/showpost.php?p=23963768&postcount=257
http://forum.xda-developers.com/showpost.php?p=23960522&postcount=250
http://forum.xda-developers.com/showpost.php?p=23968691&postcount=274
Click to expand...
Click to collapse
looks like I've got my work cut out for me. Glad I have a dual boot with Ubuntu...anyway thanks for your help.
no problem. You might want to post anything further in that thread, you will probably get more help over there. But either way let us know if you succeed.
Sent from my Ice Creamed 3D
w0rdOo said:
I was running infectedROM Sense 3.0, and I had successfully set up several other ROMs via boot manager previously. Today I just installed Playground ICS to an SD slot through boot manager and I backed up my phone ROMs boot img and clicked reboot to playground. The phone rebooted and showed the splash screen. After about 10 seconds on the splash screen, it shut off and won't turn back on. No charge light, regular boot and vol down + power both don't work. All I need to do is get to recovery, then I have to flash the update.zip for my phone ROM in the bootmanager folder. Can anyone help me get into recovery or the bootloader?
edit: I installed playground by installing the zip, and I didn't install any other mods/kernels on top of playground. On the other ROMs I have installed in boot manager, I installed them via a nandroid backup.
Click to expand...
Click to collapse
Do you know how many times I tried to brick this thing when I was downgrading? I almost gave up! And you do it by accident? Lucky you
Edit... Sorry bout your luck, hope all goes well.
no luck so far, I opened windows sda13 thru sdk13 and none of them found the device. i guess i'll reboot and try sda13-sdz13 lol.
Just took my phone to a sprint store, after about 30 min the repair guy came back and handed me the phone. He told me he doesn't have the tools necessary to fix it so I need to come back tomorrow, but he said I'm going to have to lose all my data in order to get the phone working again using his method. I hope the emmc_recover works tonight, or tomorrow I'll probably have hboot 1.5 and s-on
Is it possible that emmc_recover won't work because I'm on the engineering hboot?
I just realized I should probably post in the downgrade hboot thread, so I'm doing that now.
EDIT: fixed my phone flawlessly, the only reason it didn't work the first time is I forgot to pull the battery before plugging it in. Thanks again for your guys' help!
Post-trial of ICS Playground
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
rugbykj said:
w0rd,
I had the same problem with my EVO after playing around with this as well. For all others that may have this problem here was my solution...
Symptoms:
After trying to re-flash from ICS Playground to another ROM my phone was stuck at the HTC splash screen and would not do anything. I restarted into recovery and was unsuccessful; even tried to recover to my original files and after that it passed the splash screen and then the screen went black.
Resolution:
Finally used fastboot into recovery and flashed another ROM and it worked. Morale of the story use fastboot from your computer to get into recovery and Flash your ROM.
Hope this helps...
____________________
Device: EVO 3D unlocked via HTCdev
TeamWin Recovery v1.1.1
HBOOT 1.5 (ehh)
MilkRunny 3vo CDMA v.1.13
Click to expand...
Click to collapse
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
w0rdOo said:
I appreciate the reply. However, the problem I had was with one specific release of playground which bricked my phone once installed. I couldn't boot into recovery or the bootloader; the screen wouldn't turn on no matter what. Fastboot won't work from this state. The only way to unbrick at that point without going to a sprint store is to use the emmc_recover tool that's part of the hboot 1.5 downgrade process (in case this happens to you or anyone else, you have to follow step 3 ONLY in the downgrade process in order to recover from bricking your phone)
Click to expand...
Click to collapse
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
wikdNoob said:
Just curious. How do you know it was a specific release, and did it happen to anyone else? Do you know the cause of it?
Click to expand...
Click to collapse
The links netwokz provided above showed me that it was a specific release. TwistedUmbrella was experimenting (and I downloaded the experimental ROM, not one of the more "stable" releases) to try to get usb mount to pc to work, and something was wrong in the build I downloaded because it wiped the emmc so I couldn't boot to the phone, recovery, or bootloader. Basically, the ROM bricked my phone in the same way that you're supposed to brick your phone when downgrading from hboot 1.5. Luckily, Twistedumbrella is a great dev who helped people who bricked their devices out. In case you're worried about running into the same issue I did, the build that bricked me is no longer online, as he's updated the experimental and regular download links.
I know it was a specific release because I wasn't the only person who reported this problem. I think it was the 1 am experimental build from 03/22. Anyway, I'm now downloading twistedumbrella's latest experimental. Back to the ROM flashing game
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
emarlatt said:
With boot manger they say you must be running the same os as your phone rom or you could brick it. If your phone rom is GB I would recommended running GB roms instead of ICS roms
Click to expand...
Click to collapse
I haven't had any sort of issue from running an ICS ROM in boot manager while running a sense 3.0/3.5 ROM as my default OS. This reported brick was caused by one specific release of playground ICS that would have bricked my phone in the exact same way if I just installed it through my recovery instead of through boot manager. Boot manager wasn't at fault here.
This thread was resolved several days ago. Can I close this thread or something? I've never tried to before so idk how to go about doing that...Well in the meantime, I guess I can just hope nobody else decides not to read page one before posting...
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Twinning92 said:
Hey guys,
I am really hoping someone can please help me out with this, as I am travelling and relying on my transformer to get me around. This is what I’ve done: basically I didn’t like the stock software, so I updated from ICS to JB, downloaded the unlock tool, unlocked the bootloader and rooted my tablet and installed TWRP recovery
From there I installed some version of Paranoid Android which kept freezing up and being jittery, so I figured I’d play it safe with a stable cm10 build, tried to flash it with TWRP and it just got stuck on the ASUS splashscreen, which I later realised was due to TWRP not being at the latest version (did I mention I am clearly a total rookie).
So I flashed paranoid back, and tried to update TWRP which I couldn’t get my head around (GooManager wouldn’t allow me to update it) so I decided to try ClockworkMod Recovery, which I downloaded this .zip and just flashed it over the top, which I thought you could do… Now my tablet won’t boot past the Asus splashscreen, nor will it boot into recovery. I could access the bootloader screen before but now I can’t.
The only thing I can think to do that worked for someone somewhere on the internet was to just let the battery run dead and then try holding down the Vol Down + Power.
Can anyone recommend anything? Or at least tell me what I’ve done?
thanks all
Click to expand...
Click to collapse
CWM is not compatible with Jellybean. Unfortunately you are hard bricked.
Why didn't you make a backup with NvFlash? If you did that you could restore your tablet.
Hello all,
Sorry to ask a "seemlingly" stupid question, but I'm having a very weird problem with my Nabi 2. It was working great until i decided to "re-hack" it. It had been rooted and Gapps installed, but I returned to stock for the OTA's last year. Now I want to go back to a rooted device.
Everything seemed to go well until the script pushed gapps to the already google friendly device. So, long story short, so many errors I decided to start over.
Using Nabilabs, I installed TWRP and installed the 1937 stock roms. Now here is where things go from bad to worse.
The system won't boot. I saw that there may be a TWRP version issue, so I used the TWRP from nabilabs (2.3.3.0) to make sure. At SOME point, not sure when or how, I lost all the mount points. I was able to get them back using TWRP 2.2.2.1but the Nabi is still soft bricked.
As of now, i am able to get any TWRP installed and can successfully restore any of the ROMS (1917 through 2127) but it won't boot. The NABI logo has no animation and it just sits there.
I have tried very permutation I can think of any nothing. Does anyone have any ideas?
Sorry for the long rambling.
mgd014 said:
Hello all,
Sorry to ask a "seemlingly" stupid question, but I'm having a very weird problem with my Nabi 2. It was working great until i decided to "re-hack" it. It had been rooted and Gapps installed, but I returned to stock for the OTA's last year. Now I want to go back to a rooted device.
Everything seemed to go well until the script pushed gapps to the already google friendly device. So, long story short, so many errors I decided to start over.
Using Nabilabs, I installed TWRP and installed the 1937 stock roms. Now here is where things go from bad to worse.
The system won't boot. I saw that there may be a TWRP version issue, so I used the TWRP from nabilabs (2.3.3.0) to make sure. At SOME point, not sure when or how, I lost all the mount points. I was able to get them back using TWRP 2.2.2.1but the Nabi is still soft bricked.
As of now, i am able to get any TWRP installed and can successfully restore any of the ROMS (1917 through 2127) but it won't boot. The NABI logo has no animation and it just sits there.
I have tried very permutation I can think of any nothing. Does anyone have any ideas?
Sorry for the long rambling.
Click to expand...
Click to collapse
Try this and also the link inside that link
http://forum.xda-developers.com/showpost.php?p=54871957&postcount=2342
I'm not sure if you should be starting with JB or ICS TWRP. You will have to figure that out. Just let TWRP do the rooting for you afterwards.
Awesome respone
aicjofs said:
Try this and also the link inside that link
http://forum.xda-developers.com/showpost.php?p=54871957&postcount=2342
I'm not sure if you should be starting with JB or ICS TWRP. You will have to figure that out. Just let TWRP do the rooting for you afterwards.
Click to expand...
Click to collapse
Man, that worked perfect. Thanks so much. You rock.
So I decided to root my phone and then flash it with Cyanogenmod 12.1 Nightly Build following this guide http://forum.xda-developers.com/droid-razr/development/rom-cyanogenmod-12-0-t2950906. Unfortunately I could not install google apps on my phone because the partition created by safestrap was too small, I am used to installing roms that completely replace the old one so I was not expecting this to happen.
So I attempted to install the nightly build on my stock rom in order to get the space that I needed. I made a back up to my SD before formatting the stock rom and attempting to flash nightly to it. However when I turned my phone back on it would boot and then display the android lying on its back with a exclamation mark inside of a triangle. I worked out how to get to the recovery menu from here and attempted to restore the safestrap back up from there but it did not work. I then attempted to update using the cyanogenmod 12.1 zip, at which point I was presented with "installation aborted", I trawled these forums looking for the retail rom, which I found and they gave me the same result. I have tried using the RSD Lite to flash it back to stock and the result is an immediate fail.
In the AP Fastboot menu it was displaying that the battery was ok but that it could not programme. Now, because the amount of time that I have spent trying to fix it, it is displaying that the battery is low and therefore I can no longer flash it.
Can anyone help?
First of all, you need to charge it.
There's a thread, here somewhere that might help you to do so.
Either get a factory cable or you might need to work with your usb cable.
Once you have power, get the right ROM and flash it using RSD.
Its been really long since I had a Razr, but one thing is for sure, you need enough juice in battery.
Tapped from my Moto X
crypticvoid said:
So I decided to root my phone and then flash it with Cyanogenmod 12.1 Nightly Build following this guide http://forum.xda-developers.com/droid-razr/development/rom-cyanogenmod-12-0-t2950906. Unfortunately I could not install google apps on my phone because the partition created by safestrap was too small, I am used to installing roms that completely replace the old one so I was not expecting this to happen.
So I attempted to install the nightly build on my stock rom in order to get the space that I needed. I made a back up to my SD before formatting the stock rom and attempting to flash nightly to it. However when I turned my phone back on it would boot and then display the android lying on its back with a exclamation mark inside of a triangle. I worked out how to get to the recovery menu from here and attempted to restore the safestrap back up from there but it did not work. I then attempted to update using the cyanogenmod 12.1 zip, at which point I was presented with "installation aborted", I trawled these forums looking for the retail rom, which I found and they gave me the same result. I have tried using the RSD Lite to flash it back to stock and the result is an immediate fail.
In the AP Fastboot menu it was displaying that the battery was ok but that it could not programme. Now, because the amount of time that I have spent trying to fix it, it is displaying that the battery is low and therefore I can no longer flash it.
Can anyone help?
Click to expand...
Click to collapse
Here are some usefull answers and links
http://forum.xda-developers.com/showthread.php?t=3069077
Sent from my Razr XT910
Thank you very much for your help got my cable today and I fixed it.
Now I just need to install CyanogenMod again :fingers-crossed:
Currently I have CM12 on my trusted Z3CT, and I am very happy with it - but it does seem like development of CM has sort of stopped for this device so I wanted to try PA.
My device is rooted, but flashed with Cyanogen Recovery (an ancient one, haven't updated I think since I initially installed CM12), and installing from this did not god well.
I rebooted into recovery, wiped partitions and cache and tried to install PA, which fails after about 20sec, not giving an error message. So i installed CM again without any issue.
Do i need to flash with TWRP, following this guide; http://forum.xda-developers.com/z3-...torial-stock-android-marshmallow-6-0-t3409486
or is there an easier way since my device is already rooted?
Please bear in mind that I am not that savvy when it comes to rooting and flashing. When initially installing CM i followed I guide to the letter. Going off-script would be something that I would.... not look forward to
Thanks for any help.