Related
How close are we to having a no-wipe root?
its not like u have to root and wipe everyday
EXACTLY
johnxjets said:
its not like u have to root and wipe everyday
Click to expand...
Click to collapse
lol the phone had root within hours of launch so chances are your phone will be BRAND NEW when you root it. I don't see how much stuff you could possibly put on your phone in a couple hours before you have the chance to do it. all you should have to do is sign into gmail. Apps, WIFI settings, passwords, all of it now restore when you log in automatically. i love it!
I rooted the phone last night while it was on and it didn't wipe anything. To have root, you just need to have the right files in the right places. It wipes absolutely nothing
jroid said:
I rooted the phone last night while it was on and it didn't wipe anything. To have root, you just need to have the right files in the right places. It wipes absolutely nothing
Click to expand...
Click to collapse
Every other post on the forum disagrees with you.
seriouslyjeff said:
lol the phone had root within hours of launch so chances are your phone will be BRAND NEW when you root it. I don't see how much stuff you could possibly put on your phone in a couple hours before you have the chance to do it. all you should have to do is sign into gmail. Apps, WIFI settings, passwords, all of it now restore when you log in automatically. i love it!
Click to expand...
Click to collapse
Well how about that since this stupid thing doesn't have a memory card, all of my pix, vids, etc are now in internal memory....
hah2110 said:
Every other post on the forum disagrees with you.
Click to expand...
Click to collapse
The "rooting" does not wipe - unlocking the boot loader wipes. The actually placement of the SU binary through custom recovery doesn't wipe. Unfortunately if you don't have a custom recovery loaded you need to unlock in order to proceed (thus wiping).
hah2110 said:
Well how about that since this stupid thing doesn't have a memory card, all of my pix, vids, etc are now in internal memory....
Click to expand...
Click to collapse
Does it wipe the entire internal storage or only the ~ 1G allocated for apps and such? Has anyone tried this to verify?
krohnjw said:
Does it wipe the entire internal storage or only the ~ 1G allocated for apps and such? Has anyone tried this to verify?
Click to expand...
Click to collapse
The fastboot oem unlock wipes EVERYTHING. The app storage and internal sd storage. So make sure to back up everything. When roms start coming out, if it's like the Galaxy S phone, it will only do factory reset wipe and not the internal sd partition.
krohnjw said:
The "rooting" does not wipe - unlocking the boot loader wipes. The actually placement of the SU binary through custom recovery doesn't wipe. Unfortunately if you don't have a custom recovery loaded you need to unlock in order to proceed (thus wiping).
Click to expand...
Click to collapse
Exactly
hah2110 said:
Every other post on the forum disagrees with you.
Well how about that since this stupid thing doesn't have a memory card, all of my pix, vids, etc are now in internal memory....
Click to expand...
Click to collapse
What I meant by this was the phone has only been on the market for a day so It couldn't be too hard to redo or reput back on what you already have. But once boot is unlocked it shouldn't ever be an issue again. Wasn't the n1 the same when you unlocked boot?
N1 didn't wipe SD though. Since this has no SD card wiping will wipe far more content.
Non-unlocking root possible?
Ok. Ive been playing around with the nexus s for sometime now. Im starting to think on rooting the phone. The problem is that unlocking the boot wipes the phone, something i do not want to happen.
If i understood these posts right i can get root if i boot with a custom recovery. So connecting to adb in fastboot mode and executing:
fastboot boot recovery-clockwork-crespo.img
Should do that.
If i then flash the superuser zip, will i get the phone rooted and still locked (not wiped).
Am i missing something? Almost certain i am.
Could any of you provide a guide on how to do it, please?
Thanxs,
Iñaki
Your method is worth a try. I thought you couldn't flash the custom recovery without unlocking the bootloader, but I've seen posts saying you could (but none saying they did, if you see the difference).
Sounds like you know what to do. I'd use the 3.0.0.5 recovery image, it's linked a couple of places here.
As soon as i have some free time to do it, i will test it. Though i still think i am missing something. Just wanted to confirm i was not overlooking something obvious.
fastboot won't work unless you have unlocked it.
distortedloop said:
Your method is worth a try. I thought you couldn't flash the custom recovery without unlocking the bootloader, but I've seen posts saying you could.
Click to expand...
Click to collapse
Don't flash the recovery, just boot directly from the file.
mazodude said:
fastboot won't work unless you have unlocked it.
Click to expand...
Click to collapse
Yes it does.
Edit:
I just tried this:
First I copied the su-2.3.6.1-ef-signed.zip to /sdcard, then I booted into fastboot mode with (power + volume up). The phone said
LOCK STATE - LOCKED
Click to expand...
Click to collapse
I then booted into Clockwork recovery with
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
I mounted /system and installed su-2.3.6.1-ef-signed.zip. No errors.
Of course, I noticed no differences at all, because I was already rooted. But nandroid backup obviously worked.
Edit 2:
/system/bin/su didn't have the exact permissions as defined in the install script, but I definitely had root. Was it a new version of su, or the old one? The /system/xbin/su -> /system/bin/su symlink was new, though.
I'm new to the whole thing and in fact still haven't got my phone. I'm just excited and would like to prepare myself.
As I understand it, it is the unlocking / locking of the bootloader that does the wipe. Therefore:
a) As soon as I get my phone, can I unlock the bootloader and then can I go about as if nothing has happened keeping the stock as is for a while to enjoy it that way? When I feel comfortable enough, go about rooting ... later.
b) Would leaving it unlocked cause any problem?
c) will I get updates if I leave the bootloader unlocked and so long as I don't flash custom roms?
Thanks
Paparasee said:
I'm new to the whole thing and in fact still haven't got my phone. I'm just excited and would like to prepare myself.
As I understand it, it is the unlocking / locking of the bootloader that does the wipe. Therefore:
a) As soon as I get my phone, can I unlock the bootloader and then can I go about as if nothing has happened keeping the stock as is for a while to enjoy it that way? When I feel comfortable enough, go about rooting ... later.
b) Would leaving it unlocked cause any problem?
c) will I get updates if I leave the bootloader unlocked and so long as I don't flash custom roms?
Thanks
Click to expand...
Click to collapse
a- yes
b- none that I am aware of. I've left mine unlocked. On other devices, like the Nexus One, you can't re-lock it.
c- yes
Also, there are some posts here lately saying they've been able to root without unlocking by using "fastboot boot recovery.img" (replace recovery.img" with whichever version of clockwork you've downloaded. Then use clockwork to flash the su zip that you'd put on your sdcard before fastboot.
The only post I've only seen where someone says that particular process actually worked is the one right above yours. Note that he was already rooted, but apparently had re-locked his bootloader. I've got no reason to doubt the process if he says it worked...it would be interesting to see someone with a fresh new phone report it works.
On the other hand, since I don't know of any reason to leave your bootloader locked, the only real advantage to that method is not wiping the phone with the oem unlock. If you're on a new phone, there's nothing lost with the wipe.
shrivelfig said:
Don't flash the recovery, just boot directly from the file.
Edit:
I just tried this:
First I copied the su-2.3.6.1-ef-signed.zip to /sdcard, then I booted into fastboot mode with (power + volume up). The phone said
I then booted into Clockwork recovery with
Code:
fastboot boot recovery-clockwork-3.0.0.5-crespo.img
I mounted /system and installed su-2.3.6.1-ef-signed.zip. No errors.
Of course, I noticed no differences at all, because I was already rooted. But nandroid backup obviously worked.
Click to expand...
Click to collapse
That's a good find. First I've ever read of just booting from the recovery image. Does the recovery image file need to be on the phone to do this?
shrivelfig said:
Edit 2:
/system/bin/su didn't have the exact permissions as defined in the install script, but I definitely had root. Was it a new version of su, or the old one? The /system/xbin/su -> /system/bin/su symlink was new, though.
Click to expand...
Click to collapse
The 2.3.2 update changes the permissions of the /system/bin files. Maybe you'd applied that and didn't notice it had changed them?
Fastboot oem unlock, does this do anything else except for rooting your phone, unlocking the bootloader and wiping all your data?
If it doesn't do anything else, there is no harm of rooting your device when you get it, right? You won't notice it?
distortedloop said:
That's a good find. First I've ever read of just booting from the recovery image. Does the recovery image file need to be on the phone to do this?
Click to expand...
Click to collapse
Nope. I think the fastboot command copies the image to the phone first, and then boots it, apparently without any flashing.
The 2.3.2 update changes the permissions of the /system/bin files.
Click to expand...
Click to collapse
Yes, I discovered that when I lost root
When I applied 2.3.2 I did the whole shebang with backup, unlock, flash, su, busybox, relock and restore. After all that I discovered that I could boot the phone directly into Clockwork from a Windows command prompt. I did a nandroid backup and fix permissions just to test. Hard to tell who fingered the su permission last
I'd test more, but right now I'm loath to unroot.
Androyed said:
Fastboot oem unlock, does this do anything else except for rooting your phone, unlocking the bootloader and wiping all your data?
Click to expand...
Click to collapse
It doesn't actually root. It just unlocks (so that you can flash non-standard stuff, like root) and wipes.
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
roadblock217 said:
I'm fairly new to the modding area, I'm familiar with the VZW S3 and S4, but upgraded to an M8...I rooted, got S OFF with firewater, and booted into twrp...BUT somehow the main factory image was deleted, and I can only boot into twrp..it stays at the HTC logo if I just let it boot...help!!
Is there something similar to Samsung's ODIN mode that I can just reflash a factory image?
Click to expand...
Click to collapse
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
Tried..doesnt work for me
I can get it to boot past the recovery area, but only stays on the white screen with the green HTC logo...
EDIT:::
I want to try it again, but now somehow I have S ON....and it says TAMPERED, below that UNLOCKED in fastboot..
Really frustrated..
Dragbike Racer said:
I'm not sure if this will help but try reading this thread, http://forum.xda-developers.com/showthread.php?t=2718562
Hope this will help.
Click to expand...
Click to collapse
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
You can get into recovery...it won't let you restore a back up or nothing ?
Sent from my HTC6525LVW using XDA Premium 4 mobile app
---------- Post added at 12:22 AM ---------- Previous post was at 12:17 AM ----------
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
Maybe sonic can get you s-off if all else fails with his java card. I'm not sure in your situation but I know he can do it as I used it. But I would use that as last resort
Sent from my HTC6525LVW using XDA Premium 4 mobile app
roadblock217 said:
When I try this again, it keeps telling me it cannot open the file...i copy the fastboot text so that it is correct...
How can I get S OFF back if I can't boot to any rom??
Click to expand...
Click to collapse
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
andybones said:
So you were S-OFF and you somehow got turned to S-ON...??
I would say flash the RUU and call it a day, but we don't have one and the one we do have you need S-OFF..
best bet?
get into fastboot/bootloader, and put on a custom recovery.
then, get the TWRP nandroid of the OTA, restore to that.
then, weaksauce/S-OFF
and then you should be back to normal.
If adb/fastboot is not working, I suggest you re-install your drivers, worked for me when I didn't think it would.
opion 2
get TWRP on with fastboot
then
adb sideload any ROM to it and then get back to S-OFF
since you are unlocked you should be ok to do this without being htc dev unlocked.
you could also try htc dev, but i think that is locked.
sorry trying to think of anything else.
Click to expand...
Click to collapse
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
roadblock217 said:
I got TWRP back on, but where can I find a nandroid of the OTA? I tried doing a regular backup before things got weird but would not let me...Now I see the bug that doesnt allow to mount system...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2725001
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
roadblock217 said:
Thanks...just downloaded and am going to try...
What I'm concerned about is not being able to mount /system now...this is so weird
Click to expand...
Click to collapse
because of this, it most likely will not flash the nandroid then as system is a big part of the ROM and needs to be mounted.
you may have to do what was explained earlier and wipe the Internal, and then you may be able to re-do these steps.
so first try it out.
if it doesnt work, I would then wipe the 5 things instead of the 4
1) data
2) cache
3) dalvik cache
4) system
5) Internal storage (this will remove all your internal storage!)
then reboot from recovery into bootloader, then back into recovery and see if system is mounted, if it is, you can go ahead and either do the nandroid backup or an adb sideload. -- your choice
now,
if NONE of that works,
download the "RUU" that was put together and that *should* fix you right up.
andybones said:
http://forum.xda-developers.com/showthread.php?t=2725001
Click to expand...
Click to collapse
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
roadblock217 said:
Nope won't work. I think it's because there is no marker folder for the m8 in my SD card where I store my backups. I tried making one, and it won't register that there is a folder there...
Click to expand...
Click to collapse
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
andybones said:
yes.. yes it most certainly will work as my ROM is based off that precise nandroid backup...
this is something you should have had backed up..
but, make yourself a dummy nand backup to create the folder..
just don't backup anything except.. data or cache, just pick one thing. and it'll create the folder for you (tip: backup EVERYTHING (Internal., SD-Card, anything important, etc) when playing with beta ROMs. ESP AOSP beta ROMs..
the folder that gets created will be the same throughout your entire stay on the M8 using TWRP, it will never change (well that phone anyway, if you get a refurb or w.e. obv it will be different, but that phones folder markers will never change within TWRP, so it's to your benefit to have this backed up and ready to go...)
Click to expand...
Click to collapse
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
roadblock217 said:
Tried it again and again...used a different computer and it WORKED...Thank you so much for your help andybones!
Click to expand...
Click to collapse
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
andybones said:
Awesome!
Very welcome.
So what was the result fix?
Did you have to wipe Internal from system not mounting?
Or did the adb sideload work?
Also once it flashed it loaded up if you did not have to wipe Internal, was your storage still there?
Glad that your back up and running.
Click to expand...
Click to collapse
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
roadblock217 said:
I had to flash the RUU but it finally worked and was applied..I'm honestly thinking of holding off on doing more to it until I learn more!
Had to wipe pretty much all except my sd card, rebooted to bootloader and back to twrp and it allowed me to write to system. BUT I couldnt get any rom to flash (when I did, it hung on the HTC logo as usual, but the aroma installer said that it was successful..so I gave up on that and did the RUU on a different computer and its back to normal.
Click to expand...
Click to collapse
It's possible after so long you didn't give the ROM long enough to boot up?
Sounds like RUU might be a cause from flashing AOSP, threads like this are good to warn people, and for when it happens to others, they can read this and know what to do. Maybe think of a new title that could help those in a search to find this thread?
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
I'm S - offed through sunshine (gotta love them guys) and had temp root with stock recovery, I assumed the lollipop update would fail but late last night it updated and I lost root. Any idea how to root again?
Well u have s off so flash twrp then flash su
Sent from my Nexus 6 using Tapatalk
How to flash su
Sent from my Xperia U using XDA Free mobile app
The issue is I don't have access to my personal computer for the weekend. Any other way to flash twrp? Flashify says I need root so it won't do it. Twrp manager I'm leery of because I heard the partition it puts it in is wrong thereby bricking the phone.
Unfortunately I don't believe Jcase has Sunshine working for lollipop yet... But that doesn't mean all is lost, just means you have to go a different means and you need to know how to use adb commands. Follow this address below and you will have a custom recovery and then you can install whatever custom rom or a pre-rooted LP OTA if that's all you want.
http://www.teamw.in/project/twrp2/226
Scroll down and follow the instructions under either.... 'Download - ADB / Terminal method:' or 'Download - Fastboot Method:'
You might be able to try to install the Goo Manager app from the play store to do the recovery install for you. Just not sure if that works without having root. TMWN says it just needs s-off so you may be good. Wouldn't need a computer either for that method. Just make sure you get your download of whatever rom saved on your phone before you wipe your current rom.
beeper10 said:
The issue is I don't have access to my personal computer for the weekend. Any other way to flash twrp? Flashify says I need root so it won't do it. Twrp manager I'm leery of because I heard the partition it puts it in is wrong thereby bricking the phone.
Click to expand...
Click to collapse
Download this and move it to your ext-sd card (not in any folder) using htc file manager. Rename it to 0P6BIMG.zip
https://www.androidfilehost.com/?fid=95916177934537454
Then reboot to bootloader and allow it to flash. This will give you back the latest TWRP. Boot back up and delete that zip off your sd card. IF you don't delete or rename it you won't be able to get to recovery via bootloader (it will keep trying to load that zip).
Then download this (doesn't matter to where-just remember where).
http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
REboot to TWRP manually and flash it. Bam... done.....
It's not flashing - hopefully the rename is OP6 and not zeroP6. When I go to recovery then bootloader nothing happens and if I apply from SD card from recovery it says "no package selected and access denied", I'm sure I'm doing something wrong but I don't know what.
beeper10 said:
It's not flashing - hopefully the rename is OP6 and not zeroP6. When I go to recovery then bootloader nothing happens and if I apply from SD card from recovery it says "no package selected and access denied", I'm sure I'm doing something wrong but I don't know what.
Click to expand...
Click to collapse
zero P it is...
Last question.... I hope, I can't get to twrp recovery. It just takes me to stock recovery with no option to get to a custom recovery.
beeper10 said:
Last question.... I hope, I can't get to twrp recovery. It just takes me to stock recovery with no option to get to a custom recovery.
Click to expand...
Click to collapse
Did you flash this in bootloader?
I power phone off, hold volume down and hit power. Usually at this point I have recovery, bootloader, etc, now I have no options just shows the zip running and a question to update or not.... Either option goes to not updating.
Ok - apparently sometimes I'm a little slow..... All worked incredibly well once user error was taken out of the equation. Thanks Mr. Dottat, you're truly an asset to this forum!!
beeper10 said:
Ok - apparently sometimes I'm a little slow..... All worked incredibly well once user error was taken out of the equation. Thanks Mr. Dottat, you're truly an asset to this forum!!
Click to expand...
Click to collapse
Missed the part about deleting eh? Lol.
Glad you got it sorted.
When it came to update or not to update, I assumed I had to use the volume rocker then hit the power button to invoke the action. I was trying to go volume down to get to update when in reality volume down was the action needed to deny the update!! ?
(had rooted phone running cm12 nightly earlier) So i downloaded the oxygenos file yesterday, forgot to extract and directly went to TWRP, clicked wipe (ticked everything EXCEPT internal memory) then went to the .zip file of oxygenos and attempted to flash, Obviously that failed and as a result i had no OS. Did a fastboot thing and flashed cm12 back on (already had file on phone) then extracted oxygenos, went to TWRP and wiped all except internal then flashed and successfully rebooted.
Then, I even had to flash SuperSU for root again, a new version since the one on my phone was old i guess
Here's the thing now. I have all my apps up and running, but i cant find ANY of my photos, videos or music. At no point did i forget to untick internal memory.
WHAT CAN I DO??
(kinda Newb to this whole flashing and rooting thing, apologies)
Bridge Ric said:
(had rooted phone running cm12 nightly earlier) So i downloaded the oxygenos file yesterday, forgot to extract and directly went to TWRP, clicked wipe (ticked everything EXCEPT internal memory) then went to the .zip file of oxygenos and attempted to flash, Obviously that failed and as a result i had no OS. Did a fastboot thing and flashed cm12 back on (already had file on phone) then extracted oxygenos, went to TWRP and wiped all except internal then flashed and successfully rebooted.
Then, I even had to flash SuperSU for root again, a new version since the one on my phone was old i guess
Here's the thing now. I have all my apps up and running, but i cant find ANY of my photos, videos or music. At no point did i forget to untick internal memory.
WHAT CAN I DO??
(kinda Newb to this whole flashing and rooting thing, apologies)
Click to expand...
Click to collapse
If it's gone it's gone. Forget about it.
Bridge Ric said:
(had rooted phone running cm12 nightly earlier) So i downloaded the oxygenos file yesterday, forgot to extract and directly went to TWRP, clicked wipe (ticked everything EXCEPT internal memory) then went to the .zip file of oxygenos and attempted to flash, Obviously that failed and as a result i had no OS. Did a fastboot thing and flashed cm12 back on (already had file on phone) then extracted oxygenos, went to TWRP and wiped all except internal then flashed and successfully rebooted.
Then, I even had to flash SuperSU for root again, a new version since the one on my phone was old i guess
Here's the thing now. I have all my apps up and running, but i cant find ANY of my photos, videos or music. At no point did i forget to untick internal memory.
WHAT CAN I DO??
(kinda Newb to this whole flashing and rooting thing, apologies)
Click to expand...
Click to collapse
Try mounting it to a PC and seeing if you can locate them
Sent from my A0001 using XDA Free mobile app
abhi08638 said:
Try mounting it to a PC and seeing if you can locate them
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
How do I mount?
Bridge Ric said:
How do I mount?
Click to expand...
Click to collapse
Plug your phone into the computer with a USB cable
Sent from my A0001 using XDA Free mobile app
abhi08638 said:
Plug your phone into the computer with a USB cable
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I did that of course Didn't work couldn't see anything on there I realised I had accidently unlocked boot loader AGAIN thus wiping internal stuff.
Bridge Ric said:
I did that of course Didn't work couldn't see anything on there I realised I had accidently unlocked boot loader AGAIN thus wiping internal stuff.
Click to expand...
Click to collapse
LOL!! What were you thinking while typing commands in fastboot mode?
Bridge Ric said:
I did that of course [emoji14] Didn't work couldn't see anything on there I realised I had accidently unlocked boot loader AGAIN thus wiping internal stuff.
Click to expand...
Click to collapse
How do you accidentally unlock your bootloader? Your data is gone.
Transmitted via Bacon
timmaaa said:
How do you accidentally unlock your bootloader? Your data is gone.
Transmitted via Bacon
Click to expand...
Click to collapse
I dont know if that did happen someone on OPO forums told me that it did, all i did after flashing oxygenos was flash supersu root file again and after that i noticed i have no access to writing on internal memory and i even tried what this guy on OPO forums said forums.oneplus.net/threads/need-help-urgently-no-write-access-to-sd-card-i-think.150503/page-2 and now after doing that i rebooted all i see is an O going round and round on my screen.
Im DONE with this crap OS how do i just reflash CM12 when my phone doesnt switch on but TWRP does?
Bridge Ric said:
I dont know if that did happen someone on OPO forums told me that it did, all i did after flashing oxygenos was flash supersu root file again and after that i noticed i have no access to writing on internal memory and i even tried what this guy on OPO forums said forums.oneplus.net/threads/need-help-urgently-no-write-access-to-sd-card-i-think.150503/page-2 and now after doing that i rebooted all i see is an O going round and round on my screen.
Im DONE with this crap OS how do i just reflash CM12 when my phone doesnt switch on but TWRP does?
Click to expand...
Click to collapse
It isn't the OS at fault, many people have flashed it without a single issue, sorry, but it's user error. Start from scratch by flashing the stock images, I have instructions in section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
It isn't the OS at fault, many people have flashed it without a single issue, sorry, but it's user error. Start from scratch by flashing the stock images, I have instructions in section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
You're sure i should start with section 8? Sorry, "Once bitten, twice shy"
Bridge Ric said:
You're sure i should start with section 8? Sorry, "Once bitten, twice shy"
Click to expand...
Click to collapse
Yes, that's all you need to do (as long as your bootloader is actually unlocked). It will reinstall CM11S and format your userdata so you can access it again.
Transmitted via Bacon