Related
I have done a quick search but with no joy so was wondering if anyone would be able to help.
A couple of weeks after installing this ROM I opened up Super SU where I was notified the Binary needed updating but when I clicked to update my phone just reset.
Every time I've tried since has been an 'update failed'.
I'm not sure if it's related but a couple of apps which require root have been playing up since. One even saying my phone isn't possibly rooted, AdAway I think it was.
Can I just try reinstalling Super SU or is it not as simple as that?
Any help would be gratefully appreciated!
Sent from my HTC One S using Tapatalk 2
I had the same issue.
Go here: http://forum.xda-developers.com/showthread.php?t=1903752
Download the attached file, and copy it to your sdcard. Then follow these steps:
1. Relock the bootloader,
2. Flash the stock recovery
3. Unlock bootloader again, and reflash your recovery (I use TWRP)
4, Immediately (without booting into the ROM, just restart right back into the bootloader), flash that zip file from the recovery
5. Fix the permissions (within TWRP it should be listed in "Advance" I think, not sure on others.)
I fail to see the reason for the first 3 steps....
Goatshocker said:
I fail to see the reason for the first 3 steps....
Click to expand...
Click to collapse
I don't either. But I'm just listing the steps that worked for me mate. I tried installing it without the first three steps. It didn't work. Hence this.
firefiber said:
I don't either. But I'm just listing the steps that worked for me mate. I tried installing it without the first three steps. It didn't work. Hence this.
Click to expand...
Click to collapse
I've just tried it without the first three steps and it hasn't worked for me either
I'm a bit unsure how to do the first 3 steps. I've noticed Hasoons All in One One S kit has a 'Relock Bootloader' and 'Unlock Bootloader' option so I'm assuming I can use them but I am unsure of where to get the Stock Recovery from.
Any help with providing a link to it would be gratefully received?
Dunno if you're running the One S S3 or S4. I've got the S3, so assuming you have the S3, this is the stock recovery for that: http://forum.xda-developers.com/showpost.php?p=28087059&postcount=18.
1. Get to your bootloader. Then into fastboot.
2. fastboot oem lock (in cmd). It'll restart, get back into the bootloader.
3. fastboot flash recovery recovery_signed.img (in cmd) (assuming your recovery is in your platform-tools folder).
4. Restart the phone into bootloader, then fastboot.
5. fastboot flash unlocktoken Unlock_code.bin
IMO, that's a lot simpler than using that all-in-one thingy. It confuses me.
Just reflash the rom and then right after flash the zip that firefiber linked too.
Darknites said:
Just reflash the rom and then right after flash the zip that firefiber linked too.
Click to expand...
Click to collapse
I am tempted to try this but don't want to lose all my data and have to re-install all my apps.
Steveh8204 said:
I am tempted to try this but don't want to lose all my data and have to re-install all my apps.
Click to expand...
Click to collapse
Sod it I've done it, seems like the simplest way to do it even with the app re-installs.
Thanks for everyone's advice!
Sorted now, rooted again.
Just out of interest why did it just become 'unrooted' and what's the chances of it happening again?
Sent from my HTC One S using Tapatalk 2
It happened a couple times to me for no apparent reason. So, it may happen again. Best insurance is 2 nandroids on sdcard. Just in case one is bad. Obviously not of same rom. And copy of nandroid/s and sdcard bu on pc. This practice has saved me numerous times over several years of flashing.
Hi, I recently decided to root my Nexus 5 using this guide on youtube: /watch?v=J1AKqrrf-5o
But after I'm all done with the rooting process, I noticed that my Nexus 5 has lost its LTE signal. Now it onlyy uses 3G. I managed to put it back on LTE by doing: *#*#4636#*#* and changed my prefered network, but by doing so, I lost my service with T-Mobile. Can't call or send messege with LTE on.
Please help me! I'm very new to Android and rooting but this first experience is not so good. Can you tell me what went wrong? Also, I rooted using the Linux guide.
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
You might need this first. http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
Rooting alone won't mess up Wi-Fi. Don't use you tube use this http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
danny2146 said:
Many thanks, but I what can I do now? I don't want to sound like a jerk but what can the link do if I already rooted using the youtube guide (sorry again if that does sound jerkish).
Click to expand...
Click to collapse
That's why I have you the second link
If all else fails flash the google stock images
Agreed. A root alone should not have caused an issue with your radio unless something went incorrectly. I would ( personally ) flash Google's stock nexus images and then possibly try again. Gaining root access can be done different ways, you may need to read into other alternatives...
I don't know. I use the ChainFIre CF Auto root on Ubuntu. I did unrooted the device earlier and was able to get LTE and service to work. Though after I use this samw method again, LTE stopped working properly, so I guess something is wrong with this method. Will try the "standard" method later though, if I can get a hold of a windows computer.
Let's back track a bit. What is the goal with root? Are you wanting to keep a custom recovery? What network are you using?
If you are going to just root stock and not go for a custom rom, I'd just flash a custom recovery via fastboot then boot to recovery and flash the SuperSU zip from Chainfire. At that point, you're rooted stock. If you decide to take an OTA update then you'll just need to make sure that you have the stock recovery installed. However, it's just as easy to flash the update when one of our devs packages it as a rom zip to flash via custom recovery, if not easier really.
Frankly, at this point my knowledge about android phone is still very hazy as this is acually my first ever phone, let along rooting, but I am eager to learn. So what's wrong if I didn't get a custom recovery? I just followed the instruction that they (chainfire autoroot) have for Linux and got this. Dunno if it was something in my phone nor the root. I am on T-Mobile BTW.
Yea, I'm baffled by that method affecting anything to do with service. It should be one of the least intrusive ways to root. However, weird things happen. So where are we now? Are you still rooted with the service issues? Which update / baseband are you on? You have the correct T-Mobile APNs? Have LTE(Recommended) selected under Preferred Network Mode in Settings / More... /Mobile Networks? Shouldn't really be necessary to mess with changing stuff in the Hidden Menu in this instance.
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
danny2146 said:
I'm on T-mobile Nexus 5 KitKat 4.4.2, with LTE in prefered mobile data. I rooted, the problem happened, unrooted this morning, the problem gone, rooted again with same method, the problem came back. I think I have the right APN since there are two with T-mobile options and I have tried both of them. As of now, I am still on root, but thinking of unroot it again...
Click to expand...
Click to collapse
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
es0tericcha0s said:
Still scratching my head over that, as the whole idea of Chainfire's auto root just literally is only supposed to install the SuperSU app and the binary and make no other changes. Obviously that isn't the case for you though. Are you unrooting via the settings in the SU app or via reflashing the stock img files?
Click to expand...
Click to collapse
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
danny2146 said:
I used the stock flashing method. I only unrooted it though, not lock the boot loader.
Click to expand...
Click to collapse
Ok. So at this point, I would have the SuperSU zip (contains the SuperSU app and su binary) http://download.chainfire.eu/381/SuperSU/UPDATE-SuperSU-v1.91.zip on your phone, then fastboot a custom recovery like TWRP http://techerrata.com/browse/twrp2/hammerhead (fastboot flash recovery nameofrecovery.img), boot into recovery, and flash the zip. No need to wipe anything. Should just be able to flash and go. Then open SuperSU and make sure the binary is updated.
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
danny2146 said:
I'm sorry but how does one flash a custom recovery? Do I need a PC alondside or I can just do it entirely on my phone?
Click to expand...
Click to collapse
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
es0tericcha0s said:
I included the command in the parenthesis in the last post.
In bootloader mode on the phone, of course, flash from PC, with the file in your fastboot folder:
fastboot flash recovery nameofrecovery.img (note - you can change the name of the file you download to whatever, as long as you leave the extension .img alone. ex: twrp.img)
If you are rooted already or still, you can flash from the phone either via the GooManager app https://play.google.com/store/apps/details?id=com.s0up.goomanager like this:
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will install the recovery automatically.
or
(Rooted only) You can also use the app Flashify to flash the .img file directly from the phone. https://play.google.com/store/apps/details?id=com.cgollner.flashify
So yea, to solve your issue, I think it would be best to just start clean/stock, then go with the custom recovery flashed from PC + SuperSU zip method. If you can fastboot the other files to return to stock, this is no different and very quick. Should not take more than 5-10 seconds to flash the recovery. The whole operation, starting from scratch should take make 3-5 minutes to flash recovery, boot to it, flash the SuperSU zip then reboot, assuming you have fastboot set up properly and the 2 files you need downloaded already.
Click to expand...
Click to collapse
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
danny2146 said:
I don't know , but this is very interesting. I now suspect that the problem is from T-Mobile's end, not mine, nor the root. I just dug into my mom,dad's phone and what did I find? 3 goddamn G! Not LTE. But when I tried to force the thing to get LTE, it disconnected from the service. However, when I moved to another location this evening, both the LTE and service came back. I think something odd is happening either in my neighborhood or T-Mobile service. Anyways, seems like nothing of major, might have to have a talk to T-Mobile about this.
But last question, with my CF root now, how can I know if I already have a custom recovery yet? And which one? You know for if I want to flash a ROM in the future. And thank you for your help!
Click to expand...
Click to collapse
Just boot into recovery and see what you have.
If you used CF-Root, then it would not have installed a custom recovery. This is something that you would have done on your own and not likely to have forgotten. If you root access is working properly, I'd suggest installing TWRP from the GooManager app as it's pretty easy and no PC required.
http://teamw.in/project/twrp2/205
Then make a nandroid back up of your phone and make sure to back up the EFS folder too and save them to a safe place. You can back that up in TWRP or from the method described here:
http://forum.xda-developers.com/showthread.php?t=2514095
Let's back up here. Why do you think you need root if you have no idea what you are doing? Are you just rooting because you can or do you have a real purpose?
Sent from my Nexus 5
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
the exclamation point is the stock recovery. once you take in an ota, it removes both root and your custom recovery. to get your custom recovery back so that you can flash a bootloader(and the supersu root binaries). you can flash a custom recovery while youre in your bootloader via fastboot on your desktop.
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Yeah just realised that. Sorry its my first post
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
why don't you try twrp maybe you can flash twrp then remove the file then go back to cwm
Sent from my Nexus 5 using Tapatalk
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
luppas said:
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
Click to expand...
Click to collapse
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
simms22 said:
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
luppas said:
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
Click to expand...
Click to collapse
adb version and fastboot devices is different. adb is not fastboot and you can not use adb as fastboot. fastboot is fastboot.
simms22 said:
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
Click to expand...
Click to collapse
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
luppas said:
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
Click to expand...
Click to collapse
glad you got it
Hello, I seem to have soft bricked my tf700.
I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either
I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.
gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh
Hey, I'm having a problem with my recovery after I installed the latest android version(also installed custom rom and elementalx kernel, but I don't think it has anything to do with it), when I try to flash recovery, it works basically, but whenever I start the phone it automatically goes into recovery, and the only way to fix it is to flash another boot.img file, it reboots fine when I do it, but then I don't have recovery only the dead red triangle thing(please don't give me the power+vol fix, that's not the solution I'm looking for, as its not a very useful recovery), I tried to flash few recoveries/other boot.img files, but none of them boot regulary + recovery is working..
I doubt its a problem with the boot.img I try to flash, because I tried so many and it didn't worked, anyway, I need someone to help me with that, thanks a lot.
Using android 5.1.1 btw.
Be specific in detailing what you've done and the results. The way you're describing things leads me to think that you're not really clear on what you're doing.
Wakamatsu said:
Be specific in detailing what you've done and the results. The way you're describing things leads me to think that you're not really clear on what you're doing.
Click to expand...
Click to collapse
To shorten it, I have 2 booting options, the first one is regular booting with the bad recovery(red triangle), the second one is working recovery, but when I boot it automatically goes to the recovery after the google logo screen, and I can't get past that, tried many recoveries versions, but nothing worked. And yeah its been more than a year since I last touched it, so I don't remember everything as I used to.
Again, your description is extremely vague and is telling re: your knowledge. Provide file names, versions, commands used, logs, error messages, etc.
Wakamatsu said:
Again, your description is extremely vague and is telling re: your knowledge. Provide file names, versions, commands used, logs, error messages, etc.
Click to expand...
Click to collapse
File names of what? boot.img? I'm using flashtool if that's what you mean by commands used, logs of what? there are no error messages, only the red triangle, which I assume you know what I'm talking about, if you mean Android version, as I wrote before, 5.1.1, if you mean recovery version, tried many versions, so I don't think it has anything to do with it.
Are you unrooted and stock rom but just trying to install a custom recovery?
Sent from my Nexus 5 using Tapatalk
Sounds to me like the recovery is being flashed to the boot partition instead of the recovery partition, so when you try to boot normally it boots the recovery and when you try to boot to recovery there isn't anything there.
msacco4 said:
File names of what? boot.img? I'm using flashtool if that's what you mean by commands used, logs of what? there are no error messages, only the red triangle, which I assume you know what I'm talking about, if you mean Android version, as I wrote before, 5.1.1, if you mean recovery version, tried many versions, so I don't think it has anything to do with it.
Click to expand...
Click to collapse
You should not be flashing your phone because you have absolutely no idea what you're doing or trying to do.
Wakamatsu said:
You should not be flashing your phone because you have absolutely no idea what you're doing or trying to do.
Click to expand...
Click to collapse
+1 to this
Uninstall the toolkit and go read a fastboot guide
Sent from my Nexus 5 using Tapatalk
Installed the old and beautiful 4.4 android again, flashed recovery and everything else with no problems, and everything works great, thanks for the fastboot guide tips.