Hi,
I have an Amazon Fire HD 7(Ariel).
I wanted to get Android 5.2.2 on this and root it so I could get GAPPS and many more.
My Fire was on 4.5.5 so I used this guide to downgrade to 4.5.3 :
http://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
All went well and I followed all the instructions on the guide. I got root, installed TWRP and now I wanted to install lollipop.
So I followed this guide :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I went to TWRP, flashed everything and in the end, when I had to reboot to recovery, I accidentally swiped the "Swipe to install SuperSU" prompt.
Now my Fire is stuck on a black screen. It won't do anything when it's connected to a computer except connect/disconnect constantly.
I think it's in a bootloop where the screen does not turn on.
All I see on the few moments it stays connected in Device manager is MT65XX Preloader.
Do I need to get it to fastboot ? Do I need to buy a factory cable ?
What can I do now ?
Trix123 said:
. . .
All went well and I followed all the instructions on the guide. I got root, installed TWRP and now I wanted to install lollipop.
So I followed this guide :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
I went to TWRP, flashed everything and in the end, when I had to reboot to recovery, I accidentally swiped the "Swipe to install SuperSU" prompt.
. . .
What can I do now ?
Click to expand...
Click to collapse
Problem wasn't installing SuperSU, which was correct thing to do. See below.
dardack said:
I bought a used one off eBay. Booted up fine. Side loaded king root. It failed to root. After settings screen was blank flickering. So I rebooted. Same flickering. So booted into recovery and did factory reset. Now it's in boot loop. It gets to upgrading then back to fire logo. Then starting applications then back to logo. Then stays on logo. Been 30 minutes. Tried twice. Any help.
Click to expand...
Click to collapse
Sounds like Amazon OTA updated you at just the wrong time.
If you haven't been following these forums, see this. Sorry to say, you guys are bricked. If you're still under warranty, contact Amazon for replacement.
Hmm. I disabled OTA updates via JMZ FireTools on 4.5.3. That shouldn't have happened.
Well, is there anything I can do as a last resort without replacing it ?
It has been constantly rebooting. It gets recognized as MT65xx preloaded in Device Manager, goes offline and comes back on again ?
I've let the battery drain completely, so what do I do now ?
If you can help me get it into fastboot or adb then I can fix it myself.
-Thanks.
Trix123 said:
Hmm. I disabled OTA updates via JMZ FireTools on 4.5.3. That shouldn't have happened.
Well, is there anything I can do as a last resort without replacing it ?
It has been constantly rebooting. It gets recognized as MT65xx preloaded in Device Manager, goes offline and comes back on again ?
I've let the battery drain completely, so what do I do now ?
If you can help me get it into fastboot or adb then I can fix it myself.
Click to expand...
Click to collapse
You overrode and wiped JMZ's OTA block when you upgraded in TWRP. The best explanation is in the post I linked to above. If you look at other threads you'll see this happened to several people yesterday. You can't get out of the loop, so can't get into fastboot or adb. All you can do is contact Amazon for a replacement for a bootlooping tablet. (If you can't think of a plausible explanation, wait a few days until tablet would get update (which it can't, of course) and blame it on that.)
DoLooper said:
You overrode and wiped JMZ's OTA block when you upgraded in TWRP. The best explanation is in the post I linked to above. If you look at other threads you'll see this happened to several people yesterday. You can't get out of the loop, so can't get into fastboot or adb. All you can do is contact Amazon for a replacement for a bootlooping tablet. (If you can't think of a plausible explanation, wait a few days until tablet would get update (which it can't, of course) and blame it on that.)
Click to expand...
Click to collapse
I contacted Amazon and they will be sending me a replacement.
Is there any way to make this tablet work again ?
That way, I could just cancel the replacement from Amazon and that would save a lot of time.
Thanks.
Help me please )':
Hello i am french sorry for me english
i have identical problem
What would I say in sav amazon for replacement my kindle fire please :l
Thanks you !
Related
Hi,
I need help guys.
I have S4 and I was trying to mess with it and now I don't have it at all. (pic 1)
the Samsung logo and unlock lock icon are as far as my phone goes now, and after that u cant even power it off u have get battery out. (pic 2)
I am able to go to download mode (pic 3)
and I was able to get to there (up+menu+power key), but now I cant even go there. I get black screen when I am trying to do it. (pic 4)
Thanks for your time,
Ps. Help me
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
answer
Eeiden said:
Did you flash a ROM? In you pictures it appears that you can still get to recovery, is that true? What steps did you take for root? We need more information.
Click to expand...
Click to collapse
I was trying to flash rom, I was trying to make in international phone so it could work in Europe with out any Verizon build in stuff, just pure Samsung.
I can go do download mode, I was able to go for recovery before. That why there is the 4th picture, in stead of regular recovery a had that "teamwin" screen. Now when I press up menu and power is saying its going to recovery boot but then it resets it self and going back to Samsung unlock icon screen and just stays there...
You hold volume down + power to get to download mode. Then connect to a pc and download the all in one tool found in the development thread. Ignore the messages about having your phone in USB debugging and tell it to flash twrp 2.6.0.0. If it doesn't take In download mode, try rebooting your phone while it tries to flash twrp.
If that doesn't work flash stock with Odin and re-root and unlock the phone.
Sent from my SCH-I545 using xda app-developers app
I'm having the exact same problems right now. I tried flashing a 4.3 i9505 rom and now I can't get back into recovery and I can't boot into the OS. I can get into download mode and use ODIN, but I don't know what to do from there. I tried using the All-In-One tool to install TWRP, but it just says Device Not Found. I also tried flashing the stock sch-i545 kernel in ODIN, and it completed successfully, rebooted, and its still doing the same thing. Is there some other way that I've missed to return to stock? I'm kinda bummin here.. but thats what comes with the territory I suppose. Any help you can offer would be greatly appreciated. Thanks.
Found the factory image thread. Going to follow instructions. Will report back.
it works but not completly
So guys going back to my problem I was trying to do everything like lahma69 was trying too...
in odin was error that device not found, all off that...
but what I did, I look more online and I found this one guy...
and what I did in download mode I use odin, and in PDA selection I use this file stockroms(dot)net/file/GalaxyS4/SCH-i545/VRUAMDK_NoWipe.tar.zip
now boom... its kinda works... I am back with my os, I got the android root.
but some things are not right... my phone is very hot, maybe because its charging its self for the first time in weeks.
more important is Whats is happening right now, in boot menu I get errors, no commands, it was not able to do factory reset until I went into os and did it over there... and I cant do software update from Verizon... it goes to root and its trying but then gets error and going back to os...
and I am worry about that file that I download...
so we got little progress and lahma69 I can at least operate os and I have back stock root...
but until we will not going to make it 100% hold on with what I did...
U cant flash a rom thats not made specifically for the verizon variant (i545). The i9505 is the international version of the phone. Hence your phone not booting. Youre going to have to flash the stock mdk firmware through odin and start over (reroot, etc).
SCH-I545 using Tapatalk 2
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
lahma69 said:
sannek, I actually got it back up and running doing the same thing you did. I flashed the factory image in this thread: http://forum.xda-developers.com/showthread.php?t=2301259
I haven't noticed any problems yet. I'm fixing to reroot and flash my nandroid. I will let you know if I run into any problems.
I know you can't typically flash a i9505 rom on a verizon gs4, but the author of a i9505 4.3 rom gave me some instructions to try in order to get it working. I'm inserting a 4.3 ramdisk into a 4.2 AOSP ktoonsez verizon gs4 kernel, and replacing the boot.img in the 4.3 i9505 rom. I now know that I had accidentally inserted the wrong version kernel, and thats what caused my problems.
Click to expand...
Click to collapse
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
SaNNeK said:
lahma69 were u able to do software upgrade on your phone?
and I am happy for you, mine still have same problems like I mentions up there, I still get error and no command in root and I cant get software update... as soon I will be able to figure this out that will mean that my phone is 100% able to go back to Verizon that's one thing but then I will now for future because really want to make this phone a Europe compatible phone...
Click to expand...
Click to collapse
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
root problem and upgrate
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
SaNNeK said:
So I did exactly how xda web site was saying about going back to stock and all of that.
It worked, I can run to os and I have original root.
Still have couple of problems,
1.when u in recovery I see error and no command right below android guy. also I see new info in yellow color, below regular blue recovery screen option. (pic1)
2. information in yellow color is follow: (pic 2)
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the csc-code:VZN
successfully applied multi-CSC.
never see in before, don't know what to do..
3. I cant do regular Verizon software update. S4 resets it self and goes to recovery where is trying to do update but ends um saying error and then is going back to os and its saying that update was not that and that there were no changes applied...(pic 3)
I still need your help guys...
Click to expand...
Click to collapse
Did you see what I said about doing Samsung software updates? The rooting threads for the Verizon GS4 say that the new VRUAME7 OTA update can't be rooted. After flashing the stock image from oden, why don't you reroot your device according to http://forum.xda-developers.com/showthread.php?t=2290798 and then install Goomanager, click the menu key, click "Install open recovery script" and that will install TWRP recovery. From there, flash a verizon rom of your choice and all should be well, no? I only use TWRP so I can't give you any input on other recoveries. Make sure you didn't somehow get updated to VRUAME7.
township japinove
lahma69 said:
My phone seems to be at 100%. I never do software updates through Verizon so I would not know if thats working or not. After I flashed the stock image in ODIN and rerooted my device, I immediately flashed TWRP through Goomanager and reflashed my nandroid (Eclipse TW rom.) Everything is running well and my phone isn't warm. Why are you trying to do a software update? I think there is an update now that can't be rooted, so you definitely don't want to do that...
I tried several things to get the i9505 4.3 rom running on my device. You can get an idea of what I did by reading this thread: http://forum.xda-developers.com/showthread.php?t=2253528&page=779 Scroll down to post #7785 and that is mine. I never did get it to boot... Let me know if you need anything else.
Click to expand...
Click to collapse
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
SaNNeK said:
Well I am not that good with all of it... I don't know a lot of meanings of all this like TWRP, Eclipse TW rom, or what you said u did on post #7785
so I am just trying to be able to make it run like new, and then if I do that I will try to work on my s3 and practice on that...
I am beginner in it... plus my English abilities are not that great, so I really don't know which root is the best or how to do it with out messing up entire phone. I love to dig into it, and my s4 was just laying broken for past month and I worked on in today with you guys and its almost working... I almost made claim from insurance for new phone but this one starts working today..
and looks like everything is fine with it
except root errors and no commands ,I cant wipe cash because its crashing and restarting and I cant do that software update, and I have that manual multi csc note in recovery system like I mention just on top with pictures...
Click to expand...
Click to collapse
Whats your build number in Settings -> About Phone ?
lahma69 said:
whats your build number in settings -> about phone ?
Click to expand...
Click to collapse
jdq39.i545vruamdk
Working progress
SaNNeK said:
jdq39.i545vruamdk
Click to expand...
Click to collapse
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
SaNNeK said:
so when I will learn how to fix my phone to 100%.
Then I will experiment with it and try to learn and install more roots if I will learn how to fix first... so I will not panic like I did this time... I was just completely lost, and I need to take is step by step... don't get me wrong... I love doing that kinda stuff I build my first pc when I was 10 years old... back on old good windows 95
Click to expand...
Click to collapse
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
lahma69 said:
And by the way,for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
And thats the most important part, because if you do you will lose root and your ability to customize your phone. In layman's terms? You will be re-VZ-navigated.
I am having a similar issue. Got the "Samsung Custom" boot screen with no boot to the OS after clean wipe and install of Hyperdrive 7. Since then I have been troubleshooting the issue and have tried many things including the "No-Wipe Factory Image". Once complete I am still getting the Samsung Custom boot screen and no loading of the OS.
Any ideas as to what I can try.
Thanks in advance,
Tony
lahma69 said:
Do you currently have root? To check, you can run the "SuperUser" app. If you don't have it, download it from the Play store. After installing it, run it, and a box should pop up asking you for superuser permissions. Click "Grant." If a message pops up that says something like "Superuser has been granted superuser permissions," then you have root. If you don't have root, you need to get it. Follow the instructions at http://forum.xda-developers.com/showthread.php?t=2290798 . After performing those instructions, and verifying you have root, you need to download an application called "Goomanager" from the play store. After installing and opening it, click your "Menu" key (bottom left hand corner of your phone.) A menu will pop up. Click "Install open recovery script." Click Yes or Ok to all the pop up messages. After that completes, you will have TWRP recovery installed. Your recovery is what you boot your phone to in order to flash new roms, kernels, etc. In order to boot into recovery, turn off your phone completely, click and hold your volume up button, and power on your phone (while still holding volume up.) You should see some tiny blue text pop up in the top left hand corner of your screen that saying "Opening recovery" (or something to that effect.) Once you see that text, you can let go of volume up, and you will boot into TWRP. Let me know if you get this far...
And by the way, for the love of God, do not do any Samsung system updates.
Click to expand...
Click to collapse
as my understanding its not.. I just did that no wipe recovery...
sorry I was out of town today... so I assume I will have to do root but which one is the best? there is so many different ones...
I found the following post while doing my daily read thru all the other forums and some people are saying that it has rescued them from wrong TWRP flash and Unrecoverable Bootloader errors.
I would try to do all the other methods available first but if you are completely bricked then you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
flumpster said:
I found the following post while doing my daily read thru all the other forums and some people are saying that it has rescued them from wrong TWRP flash and Unrecoverable Bootloader errors.
I would try to do all the other methods available first but if you are completely bricked then you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Flumpster, I was going to start a separate thread to take my brick issues out of your dev thread and saw your thread here. So the option here is to reboot into fastboot, basically wipe everything and then flash the system blob from a stock ROM.
My main question is what if the person is on a TF300T bootloader, in my case 10.6.1.8. Would flashing the latest stock Asus JB ROM over 'system' for the TF200 replace the bootloader as well?
trogdan said:
Flumpster, I was going to start a separate thread to take my brick issues out of your dev thread and saw your thread here. So the option here is to reboot into fastboot, basically wipe everything and then flash the system blob from a stock ROM.
My main question is what if the person is on a TF300T bootloader, in my case 10.6.1.8. Would flashing the latest stock Asus JB ROM over 'system' for the TF200 replace the bootloader as well?
Click to expand...
Click to collapse
To answer myself, yes it does replace the bootloader. The latest ROM on Asus (from last Dec 2012) installs bootloader 1.00e ww_epad-10.4.2.18-20121122 a03
I installed stock TWRP 2.5.0 here for JB based on this thread and was able to get into TWRP and install the Hairybean Upgrade for 2.3, followed by the HB 2.3, and am now booting into the ROM. W00t! Great link in the OP flumpster.
trogdan said:
To answer myself, yes it does replace the bootloader. The latest ROM on Asus (from last Dec 2012) installs bootloader 1.00e ww_epad-10.4.2.18-20121122 a03
I installed stock TWRP 2.5.0 here for JB based on this thread and was able to get into TWRP and install the Hairybean Upgrade for 2.3, followed by the HB 2.3, and am now booting into the ROM. W00t! Great link in the OP flumpster.
Click to expand...
Click to collapse
Ah. I see you have it fixed now.
Ignore the pm I just sent you then.
I have the same issue and i solved it with your link
Can't get in to fastboot?
I just cant get in to fastboot mode.
KingJelle said:
I just cant get in to fastboot mode.
Click to expand...
Click to collapse
adb reboot bootloader
When in recovery.
I just got a used prime and was trying to root/unlock/custom recovery/rom but I think I did something wrong.
This process seems a lot more delicate and volatile than my phone
I installed cwm through the CWM Rom Manager app after unlocking and rooting both of which went smoothly and device booted, and the device was properly rooted. After flashing recovery through CWM Rom Manager app I am ASUS boot screen
The one with "the device is unlocked" in the upper right corner and just sits in that state indefinitely. Can't do anything other than restart and get back to that screen. Any ideas?
hypocritelecteur said:
I just got a used prime and was trying to root/unlock/custom recovery/rom but I think I did something wrong.
This process seems a lot more delicate and volatile than my phone
I installed cwm through the CWM Rom Manager app after unlocking and rooting both of which went smoothly and device booted, and the device was properly rooted. After flashing recovery through CWM Rom Manager app I am ASUS boot screen
The one with "the device is unlocked" in the upper right corner and just sits in that state indefinitely. Can't do anything other than restart and get back to that screen. Any ideas?
Click to expand...
Click to collapse
Unfortunately you never read up on anything before attempting it. There are warnings everywhere on this forum saying not to use cwm on the prime and not to use rom manager and goo manager.
The last official version of cwm on the prime was for the ICS bootloader and if you flash that recovery onto jellybean bootloader then chances are you are going to brick yourself. Rom manager doesn't check what you are on and just installs the ICS version anyway. I reported this to Koush 2 years ago and he did nothing about it.
If you can't get to the bootloader or recovery by holding down volume down and power the same time and you also don't have nvflash backups then I am afraid that you are hard bricked.
There are only 2 options. Either pay Asus to fix it which will cost you more than you paid for it or you buy a motherboard off ebay or one with a smashed screen but still working and swap the motherboard out.
hypocritelecteur said:
Drat. Is there absolutely no chance, no method that might possibly work? No system dumps or backups or anything I can snag from another user to bootstrap my way back to functionality? I admit I jumped the gun here defs. I've been mucking with roms and hacks for android for years and never hard bricked anything and never run into a system this volatile. Didn't realize I was even being reckless! Just a different world I guess. This is however my first tab--are they in general more risky?
Click to expand...
Click to collapse
I know how you feel mate as before getting this tablet I have had numerous android devices and have had lots since and this is by far the easiest to hard brick. With other devices you can mess up but normally there is a method back in (odin etc) but Asus decided to tie it down completely.
The nvflash guys did a great job to make our devices brick proof but you have to make sure that you have your backups first. No one elses backups can be used. They are specific to your motherboard.
You can pick up motherboards quite cheap on ebay and someone here on one of the recent posts even put a tf300 motherboard in there instead as it was a lot cheaper ($50). They are basically the same machines anyway.
Was it unlocked when you got it ? If it was ask the original owner if he ever made nvflash backups.
tf201 maybe bricked
flumpster said:
I know how you feel mate as before getting this tablet I have had numerous android devices and have had lots since and this is by far the easiest to hard brick. With other devices you can mess up but normally there is a method back in (odin etc) but Asus decided to tie it down completely.
The nvflash guys did a great job to make our devices brick proof but you have to make sure that you have your backups first. No one elses backups can be used. They are specific to your motherboard.
You can pick up motherboards quite cheap on ebay and someone here on one of the recent posts even put a tf300 motherboard in there instead as it was a lot cheaper ($50). They are basically the same machines anyway.
Was it unlocked when you got it ? If it was ask the original owner if he ever made nvflash backups.
Click to expand...
Click to collapse
well i tried all these thinks but i can not get into fastboot or into my OS doesn't see my micro sd card also at all it does is go back to the twrp recovery 2.6.3.0 it is wrong file in the twrp recovery all files are empty did i brick my tf201 and is it a paper weight this all it does can't back up or install anything no files and don't see my sd card also need help please
Exterminator77 said:
well i tried all these thinks but i can not get into fastboot or into my OS doesn't see my micro sd card also at all it does is go back to the twrp recovery 2.6.3.0 it is wrong file in the twrp recovery all files are empty did i brick my tf201 and is it a paper weight this all it does can't back up or install anything no files and don't see my sd card also need help please
Click to expand...
Click to collapse
When in TWRP you should have adb access if you have the drivers installed.
Try.
Code:
adb reboot bootloader
to get you back to fastboot.
I managed to install original system blob. But what now? After start I have again four options, but my Prime is not booting into system or recovery. It always hang up on starting screen with ASUS logo or wit a dead robot.
Thank you.
---------- Post added at 09:05 PM ---------- Previous post was at 08:06 PM ----------
ok, now I am totally bricked, I restarted my Prime and it is black, even backlight is dead. It only reacts to power button, when I hold it, it vibrates after a while.
Fastboot or ADB cannot contol it.
Dammit
Did you ever manage to get your system back?
I used ADB to make a backup of my TF201.
I couldn't get ROM manager to flash a new ROM - every time RM restarted the TF201 I simply got the screen The Device is UnLocked together with the graphical menu for Recovery, Android, USB and Wipe and it just sat there and did nothing.
Eventually, I pushed the CWM ZIP into /SDCARD/ renamed it to UPDATE.ZIP then tried rebooting to see if it would treat that like an OTA update - it didn't.
So then I chose the Wipe option. It sat there for ages with nothing happening.
So I then rebooted - now I get the The Device is Unlocked in the top left hand corner, the ASUS logo in the middle and the Powered by NVIDIA`TEGRA` in the bottom right but it does not boot - it is bricked!
My PC no longer sees it in ADB or FASTBOOT so I can't either flash something or restore my carefully taken backup.
It won't boot into anything other than the screen above - so the key combination for Fastboot doesn't work any more.
Prior to all this it was running stock 4.1.1 but was successfully rooted and had been like that for quite some time.
Any ideas?
Kind Regards
Steve
Hi, I have the same problem than the last message. It's impossible!! any ideas please??
Thanks
Vanessa
Hrd Bricked tf201
sdemills said:
Did you ever manage to get your system back?
I used ADB to make a backup of my TF201.
I couldn't get ROM manager to flash a new ROM - every time RM restarted the TF201 I simply got the screen The Device is UnLocked together with the graphical menu for Recovery, Android, USB and Wipe and it just sat there and did nothing.
Eventually, I pushed the CWM ZIP into /SDCARD/ renamed it to UPDATE.ZIP then tried rebooting to see if it would treat that like an OTA update - it didn't.
So then I chose the Wipe option. It sat there for ages with nothing happening.
So I then rebooted - now I get the The Device is Unlocked in the top left hand corner, the ASUS logo in the middle and the Powered by NVIDIA`TEGRA` in the bottom right but it does not boot - it is bricked!
My PC no longer sees it in ADB or FASTBOOT so I can't either flash something or restore my carefully taken backup.
It won't boot into anything other than the screen above - so the key combination for Fastboot doesn't work any more.
Prior to all this it was running stock 4.1.1 but was successfully rooted and had been like that for quite some time.
Any ideas?
Kind Regards
Steve
Click to expand...
Click to collapse
Hi Steve:
Well darn it, I'm another one with a completely bricked tf201. Without going into how I got there, I have the same situation as you... with "The Device is Unlocked" in the upper-left of the screen, "ASUS" in the center and "Powered by Tegra" in the lower right. If I boot with either just the power button, or the power botton and volume down, I get the affore-mentioned screen.
If I boot with power button and volume up, I get a completely black screen. I was very interested in whether you received a reply to your question?
I've noticed that the greater percentage of these questions, as I've described my system, remain unanswered. Not that I am complaining, but I am certainly interested in whether or not there is a remedy as of this date? I am not able to afford sending my tablet to ASUS, so would really appreciate any work arounds I could try.
Cheers man. Hope to hear from you.
Jim
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
ipsmaxes said:
so I managed to root my device without bricking it
and now I needed the twrp recovery thing so I could install cm 10.2
now I followed some tut on youtube that told me to use flashify which I did and I then downloaded some old version of twrp with it
when I rebooted my device it said safe reboot error or something.. and now it does nothing (freaking out here)
it won't turn on even when I try to reboot into recovery when I put it in my pc it shows like 10 storage devices that I need to format
pleasse help me (I had this phone for less than a week now))))))
Click to expand...
Click to collapse
First step: Don't panic!
Second step: Tell us which version of the G2 you have (carrier) and which update you had on before things went south, and also which version of TWRP you have.
Third step: Please explain what you mean by it not turning on but plugging it into the PC shows odd things.
Does that mean you CAN still get into recovery? Can you get to download mode? But either way, just stay calm. I just helped my buddy with the ATT version fix his phone from a similar issue a couple of days ago and I have also played with the Sprint version quite a bit and am familiar with LGs in general. Lemme know these things and I can help get you back on the right track.
Can you get into recovery mode?
If you can, try the factory reset and reboot your device.
Does your phone connect to adb?
If so i guess you could flash a fresh rom from there.
Correct me if i'm wrong, i am a new user with slight experience.
Same Thing Happened to Me
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
alferdjeffers said:
I'm freaking out a bit as well. I tried the Flashify method of installing TWRP and got the error message followed by a blank unresponsive phone. Got there via a "Phone Tech Kid" video explaining how to install TWRP. Plugging it into my computer results in being able to open a "drive" with one folder titled "image". The image file that I flashed is 2.6.3.2-g2vzw obtained via a link from this video:
Has anyone come up with a solution?
Click to expand...
Click to collapse
Probably would be best to start your own thread. However, what update were you on? I'm hoping that you do have the Verizon version of the G2? What error is on the screen? But generally speaking, you should be able to boot to the software update mode and re-install the stock OS with the kdz file, for most G2 things. I haven't worked on a VZW one though, only Sprint and T-Mobile ones and they're all a bit different.
Well, I guess I'm one of those now. I installed SU, SafeStrap and had root working. Except for a few minor glitches here and there, the HDX was working great. I wasn't happy with the glitches, so I thought I could revert to stock. Tried OTA, but it wouldn't completely download, so I thought I could grab the bin off Amazon or the forums. Tried that and now I've got the Black Screen of Death. BTW, I don't' have a backup slot anymore and it seems recovery has become unstable (can't create new ROM slots).
After fully powering on, the power button makes the correct sound when you try to turn it off. The volume buttons also make their indicator sounds when you hit the top and turn down/up. I still can get into Recovery and have ADB in both Recovery and when on the BSoD. What I haven't been able to do is get root back so I can do the ADB push to restore anything to working. Here's what I've tried:
initially, tried restoring to stock Amazon through recovery... this is what started my mess
got the Amazon 'device can't start' so I wiped to factory... that didn't work
tried reinstalling apollo_g_apps_ROM... that didn't work
Then i tried http://forum.xda-developers.com/showthread.php?t=2792225 - no root, so I can't do it
and http://forum.xda-developers.com/showthread.php?t=2588608 - get stopped with jcase steps
and (jcase) http://forum.xda-developers.com/showthread.php?t=2542456 - get an error that my device isn't supported
I'd like to learn how to fix this rather than just call Amazon. Been rooting/ROMing my phones for a few years (Hero was the first one) and I've had good success. (I know HDX is different... I did read the warnings, I just made a mistake and now I want to learn how to fix it.) A little explanation of what I need to do would be appreciated though.
ok
enjid said:
Well, I guess I'm one of those now. I installed SU, SafeStrap and had root working. Except for a few minor glitches here and there, the HDX was working great. I wasn't happy with the glitches, so I thought I could revert to stock. Tried OTA, but it wouldn't completely download, so I thought I could grab the bin off Amazon or the forums. Tried that and now I've got the Black Screen of Death. BTW, I don't' have a backup slot anymore and it seems recovery has become unstable (can't create new ROM slots).
After fully powering on, the power button makes the correct sound when you try to turn it off. The volume buttons also make their indicator sounds when you hit the top and turn down/up. I still can get into Recovery and have ADB in both Recovery and when on the BSoD. What I haven't been able to do is get root back so I can do the ADB push to restore anything to working. Here's what I've tried:
initially, tried restoring to stock Amazon through recovery... this is what started my mess
got the Amazon 'device can't start' so I wiped to factory... that didn't work
tried reinstalling apollo_g_apps_ROM... that didn't work
Then i tried http://forum.xda-developers.com/showthread.php?t=2792225 - no root, so I can't do it
and http://forum.xda-developers.com/showthread.php?t=2588608 - get stopped with jcase steps
and (jcase) http://forum.xda-developers.com/showthread.php?t=2542456 - get an error that my device isn't supported
I'd like to learn how to fix this rather than just call Amazon. Been rooting/ROMing my phones for a few years (Hero was the first one) and I've had good success. (I know HDX is different... I did read the warnings, I just made a mistake and now I want to learn how to fix it.) A little explanation of what I need to do would be appreciated though.
Click to expand...
Click to collapse
Okay we tried this once before with another guy that had a similar situation and it worked for him.. You need to push root via ADB even if your system is screwed. Go back to this forum http://forum.xda-developers.com/showthread.php?t=2782159 especially the first half you will find me in their posting about a Chinese root method and how to use it. It came here just before towelroot .It will push root even though your system will not boot, via ADB . Have your Wi-Fi turned off on your computer while you are using this application to do this and promptly uninstall I don't know if we ever figured out that it was well trusted but it does work. You will also find somewhere in that thread about another link to XDA that runs an application to replace the Chinese superuser with our SU... But worry about that later. btw this shouldnt have happened if you were messing with a slot and not stock slot. Just do not factory reset.
jimyv said:
Okay we tried this once before with another guy that had a similar situation and it worked for him.. You need to push root via ADB even if your system is screwed. Go back to this forum http://forum.xda-developers.com/showthread.php?t=2782159 especially the first half you will find me in their posting about a Chinese root method and how to use it. It came here just before towelroot .It will push root even though your system will not boot, via ADB . Have your Wi-Fi turned off on your computer while you are using this application to do this and promptly uninstall I don't know if we ever figured out that it was well trusted but it does work. You will also find somewhere in that thread about another link to XDA that runs an application to replace the Chinese superuser with our SU... But worry about that later. btw this shouldnt have happened if you were messing with a slot and not stock slot. Just do not factory reset.
Click to expand...
Click to collapse
Good news is, Vroot may have worked. It reported it worked, but I'm still at a black screen. I attempted the next step, which was to modify build.prop. Again, no screen, so I used ADB. I was able to pull the file to my computer and make the changes, but I can't get SU confirmed so I can put the file back.
I found this post to try as a next step, hoping I could get the screen back: http://forum.xda-developers.com/showpost.php?p=53444204&postcount=75. When I issue SU, the kindle lights up (still nothing displayed) and ADB waits. Then it times out and reports not permitted.
I guess the biggest problem right now is, I can't confirm dialog boxes b/c I can't see them on the screen. Is there a way to force SU from ADB? My thinking after that is, I could then push an Amo bin and get my screen back. Maybe that's not possible either.
?
enjid said:
Good news is, Vroot may have worked. It reported it worked, but I'm still at a black screen. I attempted the next step, which was to modify build.prop. Again, no screen, so I used ADB. I was able to pull the file to my computer and make the changes, but I can't get SU confirmed so I can put the file back.
I found this post to try as a next step, hoping I could get the screen back: http://forum.xda-developers.com/showpost.php?p=53444204&postcount=75. When I issue SU, the kindle lights up (still nothing displayed) and ADB waits. Then it times out and reports not permitted.
I guess the biggest problem right now is, I can't confirm dialog boxes b/c I can't see them on the screen. Is there a way to force SU from ADB? My thinking after that is, I could then push an Amo bin and get my screen back. Maybe that's not possible either.
Click to expand...
Click to collapse
.
Safestrap was booting?
jimyv said:
.
Safestrap was booting?
Click to expand...
Click to collapse
Yup. Still is.
?
enjid said:
Yup. Still is.
Click to expand...
Click to collapse
What was your original system version? And which safestrap version?
jimyv said:
What was your original system version? And which safestrap version?
Click to expand...
Click to collapse
OS: 14.3.2.3 (I had recently updated and I noticed another one was trying to d/l before I ran the ToolKit.)
Safestrap: Not 100% sure. I used the HDX Toolkit v0.94, so Safestrap-Apollo-3.72 at the time(?) I still have the installer and can find out exactly if need be
did
enjid said:
OS: 14.3.2.3 (I had recently updated and I noticed another one was trying to d/l before I ran the ToolKit.)
Safestrap: Not 100% sure. I used the HDX Toolkit v0.94, so Safestrap-Apollo-3.72 at the time(?) I still have the installer and can find out exactly if need be
Click to expand...
Click to collapse
Did you make a backup of stock? If you did try to restore it to stock slot. Or just grab your bin file rename to .zip ,push to sdcard along with flashable supersu . Dirty flash to stock slot.
jimyv said:
Did you make a backup of stock? If you did try to restore it to stock slot. Or just grab your bin file rename to .zip ,push to sdcard along with flashable supersu . Dirty flash to stock slot.
Click to expand...
Click to collapse
Well... thank you. I messed up my backup of stock, so I couldn't just roll back. I thought I had tried flashing a bin, but I looked again and it was something I downloaded from a forum (so either a bad d/l or bad file in general).
Anyway, I did as you suggested with a brand new Amo download and it worked. Thank you for your help and patience.
Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
trungamox34 said:
Hi,
My HDX 7" was bought last year and I immediately found a thread about SafeTrap recovery, so that I could flash a custom ROM to my HDX 7" I followed the instructions carefully and it successfully worked
But then my friend borrowed it, he didn't know about the SafeTrap and seemed to wipe all of my ROM slots. He gave it back to me when the device was still on SafeTrap. I plugged it to my laptop and found that ADB was still working, tried to push a ROM to it, but I couldn't, the storage showed 0MB so it couldn't store the ROM files.
I decided to turn it off, and when turned on, SafeTrap was gone, my HDX showed Kindle Fire logo forever.
I knew that it was hard bricked and left it until now, I thought there would be a way to restore my HDX in the future
Is there anyway to bring it back again?
Or it will be bricked forever?
Thanks!
Click to expand...
Click to collapse
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
jimyv said:
do you remember what firmware it was on?could he give you any insight into what he had done?did it have gapps with the xposed framework installed?
Click to expand...
Click to collapse
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
trungamox34 said:
I don't remember the firmware, I tried flashing another custom ROM, with some Gapps and no Xposed right after bringing it home I just wanted to make the experience like the general Android device with Google Play Store and services
Click to expand...
Click to collapse
Not to be rude but first thing's first if anybody here is going to help you you're going to have to know details and exactly what you had prior to your current state .ie answer any questions with as much detail as possible . And if it all possible find out what they did to your device . If you cannot provide any of this .I cannot provide a help . I don't know anybody that has a crystal ball I can borrow LOL
The question was had you installed xposed framework on your stock slot?
What your original firmware was?
Then you might want to add exactly what rhomb you attempted to flash?
What error did it show. Can you or can you not still get into safestrap?
First guess though I would venture to say you have a paperweight and less you can get them to warrantee it for you. Personally I would have uninstalled safe strap recovery and lock root access out before I loan my device to anybody period but that's just me