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...
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
JoeLansing said:
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
Click to expand...
Click to collapse
Flash this in twrp:
http://www.androidfiles.org/securekey.php?file=Nabi2/JmzNabi2Stock_OLD.zip
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Flash this in twrp:
http://www.androidfiles.org/securekey.php?file=Nabi2/JmzNabi2Stock_OLD.zip
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Ok, I got that. Having problems getting TWRP to see it. I tried from SD card, tried copying it into sd-ext, sdcard, external_sdcard, sdcard/twrp/backups. No luck. If I click Install from sdcard it shows me /sdcard/root.zip so I tried putting it in there but no luck when I click recovery. I tried setting permissions on the zip to 777. What on earth am I doing wrong. I spent about an hour with google searching before I came back here. I'm on TWRP v2.2.2.1
- Joe
JoeLansing said:
I had done the original root/gapps install on this. Then had problems with gapps. So I went back into TWRP and I had a restore called stockunrooted. I restore it, and when I go to reboot it says "Warning, No OS installed". Sure enough, it boots to a little Nabi logo with no motion. And just sits there. I used TWRP file manager and don't see any files in /boot after I do a restore. /boot and /system seem to restore instantly. I'm good with PC's, Networks, and Linux, but not Android hacks. Is there something I can download, push with ADB, then load with TWRP that will fix me up? I think that's how I got the STOCKUNROOTED that is already there though
Got Nabi2
Rooted with jmz?? method and also installed his gapps
Nabi wouldn't power on right without reset hole after a week or 2
Restored stockunrooted, worked fine, no more power on problem, but no root or gapps
Rooted per jmz method, worked, no gapps.
Wanted to install gapps, so restored stockunrooted again, now nothing
At least TWRP works. It's wifes though, and she isn't into just using it for TWRP.
- Joe
Click to expand...
Click to collapse
i hope ya wasnt using the mic hole on the bottom of the Unit
http://www.nabitablet.com/specs/nabi2
IF i were you i would Search the forum "nabi 2"
you will find a lot of post with downloads and things that people have done to help get their nabi 2 up and running.
HTH
I used the reset hole and I've already downloaded all the jmz files and a few more. I've read about Nabi here for hours. My last try was restoring JMZ_OLD to get back to factory. Still no WiFI. Then I tried installing the WiFI_Fix. Now it just shows a spinning Nabi logo. I rooted my 4th one today using the new Nabi Lab which I really like! My wife's is the only one that is a problem child. Funny thing is the other 3 were bought at Walmart, hers was bought at GameStop. I think from reading the Cannot Turn on WiFi is a version problem between the drivers and the kernel, but not sure. I really want to try Nabi Lab on it but I think it is old Nabi software at this point, and Nabi Lab says I should be fully updated to run it. But I can't update it without WiFi...grrrrrrrrr. Is there anything I can do to restore it to stock including stock kernel and drivers? Who knows, maybe the WiFI has a hardware problem? But I doubt it. If I use JMZ_Old, then the 2 OTA update files, then ??? I'm not sure I've tried that yet. I wipe everything between attempts. 3 more posts and I can go thank the gentelman that made Nabi Lab in that thread and tell him I tested it and it worked fine.
- Joe
I wonder if you have a Different Nabi 2 then i do ?
coz the only hole I have that looks like a reset hole is for the mic
http://forum.xda-developers.com/showthread.php?t=2050365&highlight=nabi
has a few different downloads like a striped rom a full untouched version and a full de-odexed version.
maybe try that one
.---UPDATE---
New Rom available.
Completely stock.
Not even De-Odexed.
Update 37.
SHOULD fix WiFi issues.
Flash using directions at top of post substituting this zip for the one used in the directions.
PureStockU37.zip
that is the updated 1.9.37 Current at the time of this post
Ok, I'm a moron. My reset hole is the mic, which is now pretty dead...:crying: The good news is Nabi Lab fixed my WiFi and soft brick problems. I had tried about every image out there including that one you suggested. Using Nabi Lab and flashing the hmm All Original - Won't Boot or something like that fixed it. Since I never use the mic I'm ok. I could probably replace it if I wanted to, but I'll give it a rest before I break it again.. I have 3 Nabi's, and 2 Uniden tablets. I killed one of the Unidens. The screen got worse and worse. I popped it apart and tried to reattach the 2 wires to the screen half. It started smoking and doesn't power on.. Now I might take the battery off it and see if I can solder it into the other Uniden to get longer life. I hope it doesn't get hot.
Eric Karz said:
I wonder if you have a Different Nabi 2 then i do ?
coz the only hole I have that looks like a reset hole is for the mic
http://forum.xda-developers.com/showthread.php?t=2050365&highlight=nabi
has a few different downloads like a striped rom a full untouched version and a full de-odexed version.
maybe try that one
.---UPDATE---
New Rom available.
Completely stock.
Not even De-Odexed.
Update 37.
SHOULD fix WiFi issues.
Flash using directions at top of post substituting this zip for the one used in the directions.
PureStockU37.zip
that is the updated 1.9.37 Current at the time of this post
Click to expand...
Click to collapse
that's good you got the nabi working
Now that nabi with the bad speaker ... i wonder if you can use the speakers from the dead Uniden in the nabi 2 ?
here is a thread where the nabi 2 was open up
http://forum.xda-developers.com/showthread.php?t=2024105&highlight=nabi
If you try the battery project or the speaker replacement - be neat to see pictres of it....lol
Speaker was a beer typo.. I meant the mic. I'm an old man and have no use for croaking at people over the interweb with a microphone so I'm ok.. I started a thread someplace about the Uniden tablets. I checked back and it's like 9 pages long with geeks installing Ubuntu and everything else on them. I was amazed! I'm going to get real and get an Onda V972 soon I hope. Now that I have enough posts here I will probably start a thread about buying one of them.
- Joe
Eric Karz said:
that's good you got the nabi working
Now that nabi with the bad speaker ... i wonder if you can use the speakers from the dead Uniden in the nabi 2 ?
here is a thread where the nabi 2 was open up
http://forum.xda-developers.com/showthread.php?t=2024105&highlight=nabi
If you try the battery project or the speaker replacement - be neat to see pictres of it....lol
Click to expand...
Click to collapse
Help brick
Sorry my english.
I was trying to install the GAPPS on nabi2 and messed up.
The kernel recovery screen appears with a exclamation android open.
In normal boot the screen is locked in logo nabi.
I do not have TWRP installed.
When I select fastboot protocol recognizes the PdaNet and appears as a device in windows mtp unknown.
Is there any chance to recover? Could guide me the way?
There is some recovery via APX?
RegisRicci said:
Sorry my english.
I was trying to install the GAPPS on nabi2 and messed up.
The kernel recovery screen appears with a exclamation android open.
In normal boot the screen is locked in logo nabi.
I do not have TWRP installed.
When I select fastboot protocol recognizes the PdaNet and appears as a device in windows mtp unknown.
Is there any chance to recover? Could guide me the way?
There is some recovery via APX?
Click to expand...
Click to collapse
Need to reinstall TWRP with fastboot.
Download a ROM image and restore it in TWRP.
There is an APX way but so far untested and not needed for where you are at.
Thanks for the help, after a snack could reconfigure.
I'm trying to install Freedom but is difficult. There is not enough system memory.
I updated to 2.1, but I think I'll go back to 2.05.
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.
Total newbie to all this. First time I've unlocked or rooted android.
I unlocked using the Asus unlocker. Rooted with motochopper. Then I installed fastboot and nvflash and flatline. Messed up here as I was planning to install CM11 and when I tried to install the ROM it failed. Should have read the small details. Soft bricked my tf201 and could only use apx.
Used nvflash to recover to stock jb. Re-rooted and tried to install CWM. Didn't work recovery would freeze in the loading recovery image. But I could still just boot normal into my device. Tried TWRP and had the same problem.
How do I get the recovery to work. Do I need to go back to the stock image and try all over again?
I feel like a real idiot. I was trying to install the oldest version of twrp not the newest. It's amazing what a little sleep does to figure things out. Now onto installing CM11,
JoanneDisFan said:
I feel like a real idiot. I was trying to install the oldest version of twrp not the newest. It's amazing what a little sleep does to figure things out. Now onto installing CM11,
Click to expand...
Click to collapse
Can you put SOLVED in the title of the thread..
Thx Josh
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.