Related
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
How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
toby1978 said:
How can I update to the latest 2.1.27 update on my Nabi 2? The Nabi is rooted and has TWRP as the recovery. Any help would be good! I have tried to flash a couple different Nabi 2 roms and they all fail. Thanks
Click to expand...
Click to collapse
I've got the same question. I know I'm an idiot that shouldn't have installed Gapps without having a clue, but unfortunately I did. I used the Victoria Antonio youtube video that says it does not root but does install Gapps about 4 months ago--May 2013. I'm now trying to figure out how to get the OTA update to 2.1, but I'm just lost, since it's been a while. I tried fooling around in TWRP, but again, didn't have any luck. Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
abbienormal said:
Then idiotic me touched the square button in the upper right hand side of TWRP, and it is now stuck after saying:
*Verifying filesystem. . .
*Verifying partition sizes. . .
I know this is my own fault and I apologize, but I would really appreciate some help! Thanks so very much!
Click to expand...
Click to collapse
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Thanks and sorry!
aicjofs said:
That's just the log. You didn't do anything bad. Next time just press the button again and it will hide the log.
For both of you we need some more info, what have you tried so far? What methods and files are you trying to use to get to 2.1.27?
Click to expand...
Click to collapse
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
abbienormal said:
Thanks so much for the reassurance. I did actually try to push the button aagin, but it wouldn't do anything, and after thinking I had bricked it for about a hour, I finally held down the volume -/+ and power buttons and got back to familiar territory. Sorry, again, for the completely idiotic question.
I haven't tried anything besides the standard order of operations suggested by Nabi. I downloaded the Nabi OTA software update (which took forever with our pokey internet), then clicked okay as it verified things, then it automatically rebooted with the little green Android guy with his chest open, then, unexpectedly, he's on his back dead with a red triangle sign above his chest. The tablet reboots by itself normally, and there are no changes from what I had before--none of the OTA update has taken effect. And, as a matter of fact, when I check for an update, again, (because it's still at the 2.0 release keys), low-and-behold, it detects an update and wants to download again.
I went through the process 4 times before giving up and checking with the Nabi support on FB. After troubleshooting a couple of things, they wanted to know if my Nabi 2 had ever been rooted. I shut-up then because I didn't want to be scolded, and because, of course, it's no longer under warranty if it's been rooted.
However, I got it second-hand, so I've got no warranty anyway, plus, according to the Victoria Antonio youtube video I followed, I didn't actually root it. With the teensy bit of knowledge I've got now, I'm kinda skeptical of that particular claim, but nevertheless, I still can't get it to update with the fancy new Nabi software, which I've been lusting after.
Any ideas? Obviously I'm clueless about tech lingo, so I would greatly appreciate a very simple explanation. Thanks so much for your time!!
Click to expand...
Click to collapse
If you followed any of the guides out there then you likely have gapps on your tablet(Google Play Store). If that is the case then it has modified/removed some system files. When the Nabi OTA does its thing in the "Android guy" screen(aka stock recovery) it finds files missing or modified and halts the OTA.
You have 2 options. 1) Use a modified OTA(that ignores those files), or
2) restore your backup you made during the Victoria video that has unmodified/removed files then do the OTA.
There is a caveat. The new 2.1.27 OTA uses up almost all the room on the system partition. Without removing something you cannot have a tablet with full gapps package and full Nabi 2.1.27 something will have to be deleted.
Start reading from post #1597 http://forum.xda-developers.com/showthread.php?t=1905674&highlight=nabi&page=160 it will make some more sense.
Update Nabi 2
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
rozibaby84 said:
I have no idea how I rooted the Nabi 2 tablet originally, but I know I did it because I wanted the Google Play store. I am now unable to get the update and the people at Nabi are asking if I have the Play store - I'm pretty sure they are asking this because there is some sort of issue with the update and rooted tablet. If anyone is willing to explain and work with me on this, I would greatly appreciate it!
Click to expand...
Click to collapse
Assuming you are on 2.0 right now?(2.0.5)? I'm going to base my description on that, if it's 1.9.37 or less there would be other steps.
If so you have a couple of options. I don't know which method you used to get playstore so it's a bit harder. There are 2 questions that you need to answer for yourself. Do you want Wings or the Playstore? Because as of right now it's difficult to fit them both on, and while we kind of have a method using symlinks it's not perfect yet.
So if you want to update and keep the playstore the first thing you need to do is figure out if you have TWRP installed(probably best to have version 2.6.1.0). WIth tablet powered off press and hold the vol+ and power key, navigate with the vol- key to recovery kernel and vol+ to select. If it boots to TWRP you can go on, if it boots to an Android guy you need to install TWRP. Once you have TWRP. MAKE A BACKUP! You can delete it later if you choose but make one now so you can get back to where you are if something goes wrong. I would use external SD for all of this because these are some big files.
After you have done that you can try to do this:
Download these
https://docs.google.com/file/d/0B024tOntNFbbaFJHcFRBRjVMUXc/edit?usp=sharing
http://home.comcast.net/~aicjofs/205to210libfix.zip
Copy them to the Nabi.
Boot in to TWRP and "install" both of these. You should be at 2.1 with Playstore and no Wings(You will still have one Wings app)
OR
You can restore a stock 2.1 if the above doesn't work
Download this:
https://docs.google.com/file/d/0B024tOntNFbbX1liUGN5eVU4UU0/edit?usp=sharing
Extract boot.emmc.win, system.ext4.win from the zip in to the TWRP folder on the device to internal storage(may not have room)
TWRP/BACKUPS/%serial%/2127
Or external SDcard
TWRP/BACKUPS/%serial%/2127
you will have to create the 2127 folder, and possibly the others(if you made a backup some of this will exist already) %serial% = whatever your device serial number is it's different for everyone.
Then boot to TWRP and "restore" checking boot and system only. Don't select data(it shouldn't be an option if you didn't copy data.ext4.win from the zip anyway)
This would leave you at 2.1.27 with Wings but no playstore. You can root it at that point but not install the Playstore unless you then deleted Wings.
The Product Version on the Nabi 2 tablet is 1.9.37. I am assuming that is what you were referring to when you asked if I was on 2.0 right now. I don't really care if I have the Play store or not anymore. At this point, I just want to be able to get the Nabi update and see if it addresses some of the other issues that I am having. I think that I made a huge mistake in doing all of this since I do not actually know what I am doing. I think the only reason why I got the Play store was for one specific game and I don't even remember what that game was anymore, so she will be ok without it.
I do not really understand what TWRP or anything like that is. Is there an easy way to just get rid of everything and pretty much start from scratch so that I can get the updates like normal? I know that the factory reset doesn't get rid of the rooting, unfortunately.
I am really grateful for your help! Thank you!
Error in /external_sdcard/...
I am not sure why I am getting his but I have tried every version of the Nabi2 ROM stock and custom 2.0.5 and above. It seems that I can only install previous versions to 2.0.5.
I have TWRP v2.3.3.0 installed and I am trying to get the latest 2127OTA build installed. If I revert back to stock ROM it boots fine but there a few odd going ons. One it always defaults to Mommy Mode even though I select Daddy Mode. WiFi never works even with WiFi fix. Tap sound does not turn off even though I selected to turn it off.
At this point I am fine going back to a full working stock mode as long as I will be able to get the latest OTA of the web or a working 2127OTA build.
Please advise,
Niles
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
marcusbaw said:
Hi, I have a similar upgrading problem with the Fuhu Nabi .
I am on version "1.9.37-release-keys" with TWRP 2.6 installed.
I am happy with the process of booting into TWRP, adb push etc
I just cannot get any of the updates to succeed, at the moment they all fail at the start of installation with a "assert failed: apply_patch_check("/system/app/ApplicationsProvider.apk", [and then what I'm guessing is a checksum]").
I guess this means I'm trying to apply the patch to the wrong version of current system.
I wonder if someone would be able to spell out a recommended upgrade path from 19.37 to 2.10 (possibly this would require upgrading to 2.05 as a an intermediate step)
Marcus
Click to expand...
Click to collapse
I have upgraded to the latest TWRP, 2.7, on my Nabi2 and was able to upgrade to 2.05, but I am still not able to upgrade to 2.10. Same error. Obviously some one was successful or they would not post the 2.10 file. Please advise.
Not sure if it will work for everyone, but....
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
How to Restore Backup?
78cherokeechief said:
Not sure if it will work for everyone, but after much fooling around with TWRP and the OTA update not working, I restored the backup I had made when I first rooted the nabi earlier this year, once it was done it booted into the standard nabi mode, when I logged into Daddy mode the Play store and all my root apps were gone, but I was able to install the 2.1 update that brings Wings university, and once that was installed, I then searched for updates again and it showed nabi 2 Over-the-Air Update v.2.3 (Part 1) which officially adds the Play store to the nabi 2, after that installed, I again went into Daddy mode and searched once more for updates and found nabi 2 Over-The-Air Update v.2.3 (Part 2) (which add Google Services (bloatware, honestly) and upgrades the OS to 4.1 Jelly Bean), and installed that as well. I haven't decided whether or not to re-root it, but I don't think I will, simply because there's really no need to root it anymore, since the Google Apps are there officially now. I hope this helps alot of people, since I wasn't able to find any info myself on the process, and discovered it through trial-and-error:highfive:.
Click to expand...
Click to collapse
How do I locate the backup file to restore it? I am hoping that I saved everything on my computer at home. I really just want to get rid of everything that I did to get access to the Google Play Store. I regret ever messing with it to begin with. I am trying to update my daughter's tablet, but it won't let me bc of whatever I did to get the Google Play Store about a year ago. I am almost 100% sure that I used the video by Victoria Antonio to root the tablet originally. If you are able to explain this process to me to fix it, I would greatly appreciate it. I like to think of myself as being pretty computer intelligent, but this was a big mistake!
Hey folks,
First time poster here, but have been following this awesome community for a few months now. So with that being said, I've landed myself in deeper water then I had hoped to see on my first foray into the world of tinkering on my tablet. I feel I should also disclose my epic newb moment, where in I ran headlong off the cliff with making proper (any) backups
I've been doing a lot of reading the last couple days to try and solve the issue, found lots of radical advice, but sadly haven't managed to get myself any further ahead. I was hoping that with a little list of what the TF201 is doing & what I've tried since, that you folks might be able to shed some light on what I've done and what I can try.
The Problem:
I've got a TF201, unlocked, TWRP 2.6.3.0. ADB access from command prompt. Sadly that's all I've got at this time (No OS, No fastboot). I cannot seem to install an OS now, but can still push files over to the tablet/view them. As far as I can tell, I'm have Brick 1a from this post: http://forum.xda-developers.com/showthread.php?t=1514088 . It references (CWM), so Im not sure these steps are applicable (My understanding is this is a recovery manager though I could be mistaken).
I've also explored:
[TOOL][WINDOWS-ONLY]WSG UnBricker V1.0.2
http://forum.xda-developers.com/showthread.php?t=1599991
But don't have fastboot access.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?t=2179759
But don't have fastboot access.
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
http://forum.xda-developers.com/showthread.php?t=1929189
Again appears to need fastboot access.
Etc.
So my question is, is there a process I can follow from TWRP to get me back to fastboot access? OR am I looking at the problem from the wrong angle? Any advice or suggestions would be appreciated. Apoligies in advance if this is addressed elsewhere! If there is any additional info I can provide please let me know.
***Update***
Now have fastboot access, continuing to proceed with caution. Attempting to install a rom now.
***Update 2***
Still have fastboot access, however now can't access recovery when I fastboot devices my device now shows up as ??????????? Fastboot, rather then the letters/numbers it used to show. Feeling like I've slid her a little deeper into the mud. Also a lot of "unrecoverable boot error 0x00000000"
***Update 3***
http://forum.xda-developers.com/showthread.php?t=2179759&page=2 Progress
Light_Canuck said:
Hey folks,
First time poster here, but have been following this awesome community for a few months now. So with that being said, I've landed myself in deeper water then I had hoped to see on my first foray into the world of tinkering on my tablet. I feel I should also disclose my epic newb moment, where in I ran headlong off the cliff with making proper (any) backups
I've been doing a lot of reading the last couple days to try and solve the issue, found lots of radical advice, but sadly haven't managed to get myself any further ahead. I was hoping that with a little list of what the TF201 is doing & what I've tried since, that you folks might be able to shed some light on what I've done and what I can try.
The Problem:
I've got a TF201, unlocked, TWRP 2.6.3.0. ADB access from command prompt. Sadly that's all I've got at this time (No OS, No fastboot). I cannot seem to install an OS now, but can still push files over to the tablet/view them. As far as I can tell, I'm have Brick 1a from this post: http://forum.xda-developers.com/showthread.php?t=1514088 . It references (CWM), so Im not sure these steps are applicable (My understanding is this is a recovery manager though I could be mistaken).
I've also explored:
[TOOL][WINDOWS-ONLY]WSG UnBricker V1.0.2
http://forum.xda-developers.com/showthread.php?t=1599991
But don't have fastboot access.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?t=2179759
But don't have fastboot access.
[ROOT] Urkel's Fresh Start 1.0 (Jelly Bean - Unlocked bootloaders only)
http://forum.xda-developers.com/showthread.php?t=1929189
Again appears to need fastboot access.
Etc.
So my question is, is there a process I can follow from TWRP to get me back to fastboot access? OR am I looking at the problem from the wrong angle? Any advice or suggestions would be appreciated. Apoligies in advance if this is addressed elsewhere! If there is any additional info I can provide please let me know.
***Update***
Now have fastboot access, continuing to proceed with caution. Attempting to install a rom now.
***Update 2***
Still have fastboot access, however now can't access recovery when I fastboot devices my device now shows up as ??????????? Fastboot, rather then the letters/numbers it used to show. Feeling like I've slid her a little deeper into the mud. Also a lot of "unrecoverable boot error 0x00000000"
Click to expand...
Click to collapse
Get yourself back into fastboot. I'm guessing you got there by typing adb reboot fastboot from in TWRP.
You will need to make sure your fastboot and adb exes are compatible so try these. http://flumpster.lolcakes.com/android/adb-fastboot.zip
I know they are old but I also know they worked.
Next you would have to make sure you had the correct drivers installed. I've always used these. http://www.koushikdutta.com/post/universal-adb-driver
Now follow the instructions here http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
But where he says to get the TF300 firmware etc get the TF201 instead.
EDIT : Are you also sure you are in fastboot and not in APX mode. Explain how you got to fastboot please.
Thanks for the reply flumpster, I was actually working my way through that when you posted. So now I can get into fastboot, however I have no OS installed currently. I'll keep poking at it, I feel progress is being made
EDIT
I am powering down and holding volume down. I may have a terminology issue here, but that is what I believed was fastboot.
EDIT 2
Also confirmed adb and fastboot are working, and confirmed Im using the same driver you recomended. I am now sitting with 4 options, RCK, Android, USB & Wipe Data.
With much fandangling, have got myself back to a bootable environment running the rom located here: http://forum.xda-developers.com/showthread.php?t=2147895
From what I gather I should get my backups made asap, NVflash seems to be the most commonly mentioned, but am getting an error with step 1 in wheelies. However, its another issue so I shall consider this thread case closed and go back to reading. Thanks again for the help!
I'm using a Sony Xperia Z2 tablet - SGP511 (castor_windy). It's been rooted before, bootloader unlocked and had a couple of custom ROMs at various times. I've had issues because apps like root checker say it's not rooted properly and I am not getting the full benefit of a rooted tablet.
I have recently reset it to factory and the original OS seems to have come back. I'm now trying to start again with a new ROM but can't get into recovery mode.
I've flashed TWRP recovery BUT - I can't get into recovery mode to ensure root has happened properly. I've tried getting to recovery via adb and via the hard buttons on the tablet, but the tablet either resets and loads up again or I get a triple vibrate and the LED flashes different colours.
So - i'd love to know any thoughts anyone might have? I think there's something glitchy way down underneath what I can see. I'm not amazing at this stuff - really just read a lot of forums.
I'm hoping to have TWRP working and then to root using SuperSU to ensure that the tablet is rooted properly, THEN to flash Paranoid Android.
I really really hope someone can give me a hand!
Hi all,
tl;dr: Tried to hard unbrick my Oneplus X, which was partly succesful (no OS is installed in the process, while there should be). I am now stuck with no OS and only the Oneplus recovery. I want to install an OS, but it says my bootloader is locked. To unlock it, I need an OS ==> vicious circle.
Full story below:
Recently I've decided to reinstall LineageOS on my Oneplus X because I had quite some problems with it (battery drain, apps crashing, wifi slow to connect, ...). I've done it like 5 times before on this device for various reasons, so I didn't expect any problems. I had LineageOS 14.1 and TWRP 3.0.3 installed. When I wiped everything, I wanted to flash the ROM I had ready using TWRP. However, gave an error number 7, saying that the ROM is not compatible for the device, which I am sure was. Remembering I had a similar issue a while back, I installed flashed an updated version of TWRP (3.2.2) using TWRP itself. That was successfull, but here's where the trouble began.
I noticed that TWRP didn't recognise any storage (Internal storage, SD card and USB-OTG all showed up as 0 MB) any longer. Neither could I mount any of the storages. I've tried a lot of things to solve this. After a while, I decided that the only hope left was the 'mega unbrick guide' (https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/) which claims to be able to recover any device, unless it has a hardware problem. I got good hope as I got near the end of the guide. The last step says 'Disconnect phone from PC and boot into system', but here I got stuck on the Oneplus boot logo, making me think that there is no OS installed on the device.
I can still access the recovery using power button and volume down, but the recovery that the mega unbrick guide installs, is the limited Oneplus recovery. It allows to install a ROM from the local storage, or from USB using adb sideload. When I try option 1, nothing happens, no new screen opens or anything. When I try option 2, I enter the adb sideload mode which would normally allow me to sideload a ROM using my pc. My pc confirms I'm in adb sideload mode, and I try to sideload a ROM. It starts fine, but after a few seconds, it says 'Installation failed'. I've tried stock OOS, latest OOS as well as LineageOS 14.1 that was installed before.
Another thing that I can do in the Oneplus recovery is rebooting into fastboot mode, where I should be able to flash the recovery of my choice. Again, my phone confirms I'm in fastboot mode and I try to flash or boot TWRP recovery, but I get the message: 'FAILED (remote: Device not unlocked cannot flash or erase)'. Okay, seems like the bootloader is still locked, so I should just go and unlock it using 'fastboot oem unlock'. This gives the message: 'FAILED (remote: oem unlock is disabled)'. I've been searching around a lot on the internet, and it seems like the only way to enable oem unlock, is in the OS itself in the developer settings. But the problem is, I have no OS and cannot install one because the bootloader is not unlocked... So I'm stuck in this vicious circle.
I've been searching on the internet for hours and starting to lose hope. At this point, I would be happy if I can just have any OS (OxygenOS or LineageOS or something else) running. If I have that, I should be able to take it from there.
Any help is much appreciated. Thank you very much.
Kind regards,
Jeroen
Bump
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Japeroen said:
Update:
Oneplus support could solve the problem for me! Or at least, partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
I hope I can also help other people with the same problem.
Click to expand...
Click to collapse
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
gabytzu338 said:
Greatly appreciate your feedback here. I think that I am in the same situation you were. Used what you suggested - using MSM v2.1 that you provided with the system.img, non-hlos and userdata.img from MSM v2.0. The process ends with "Download Complete" written in green but when I check "Verify" it fails exactly @system.img, userdata and non-hlos. I can't boot recovery either after these.
Do you have any clue as to why it is so?
Click to expand...
Click to collapse
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Japeroen said:
As far as I know, I haven't used the "Verify" button. Right after the green "Download Complete" line, I booted into the OOS stock recovery by pressing volume down and power button (I think? Not sure anymore, I always forget it). From there, I could install OOS with a official ROM image.
Are you sure you moved the correct files from V2.0 to V2.1? The way I knew which files to move, is by first starting the V2.1-program without any added files. Then it told me 'system.img missing' (or something like that), so I knew I had to add that. After adding that, I ran the program again and added the next file it said it was missing etc etc.
Sucks to hear your recovery process doesn't go as "smooth" (it's all relative of course) as mine.
Click to expand...
Click to collapse
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from MSM v2.0 and v3.0 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
gabytzu338 said:
Hah, did not expect an answer, I've seen your thread on oneplus forums as well, glad you were so quick to answer here. I've found the MSM2.1 uploaded in a google drive with all the files afterwards, after some long hours of searching too. Anyway, I still can't adb sideload anything, the storage seems 'corrupted' to say the least, but there are imporvements from 2.0 and 3.1 flahses. The recovery menu works flawlessly now, no artifacts or freezes, also the phone 'almost' booted. It went to the "Updating android apps" thing.
I don't really know what to do next. Recovery does not help me at all. I can't sideload anything, it renders a "protocol fault" error. Internal storage has 2 empty folders within and that's about it. Also the bootloader is locked now and I can't make any use of fastboot mode.
Click to expand...
Click to collapse
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Japeroen said:
Haha I know the feeling! But thanks to e-mail notifications.
I also thought that my storage was corrupted at first, given the symptoms I described in my first post, so I didn't expect my OPX to be revived, but hey it's still alive now.
I also had the locked bootloader-thing. The way I could unlock it, is by first installing OOS using the stock recovery (which was installed using the tool), then unlocking it in OOS, so I could install another recovery and eventually another OS.
I'm afraid I already explained the problems I encountered and the procedure I followed pretty detailed. If you have anything that deviates from this, I'm sorry to say that I can't really help you with that, even if I wanted to. Did you perform the exact steps I mentioned (including the V2.1-tool that I linked to)? What exactly do you mean with the "3.1 flash"?
It's also already 2 months ago, so I don't even know exactly what I've done apart from what I've described...
Click to expand...
Click to collapse
It was a typo, I meant v2.0 and v3.0(for oneplus 3). The op3 unbrick guide suggested that the v3.0 might work for oneplus x as well, so I tried that out too.
Anyway, I've done the process a couple more times and the phone booted untill you set the device up, when you are finished it just reboots. I can see the lock screen, I can't bring down the upper bar or enter the settings, if unlocked it prompts me to the first time set up and upon it's completion the phone reboots. I wiped cache,data did a factory reset. Now it's back with the recovery menu artifacts and not booting anymore either. I will use that tool a couple more times then I am done until further suggestions from this forum. After all, my life does not depends on reviving it, I was gonna give it to my brother, who shattered his phones' touchscreen, until he repairs his. Thank you again for replying, no need to reply to this, unless it can help my case.