Related
My buddy is having a hard time flashing a new ROM on his tablet. Currently he's running Cyanogen with TWRP.
Apparently TWRP formatted his tablet randomly and he hasn't been able to install a new ROM because his tablet won't mount the system or cache. It keeps failing. Neither system or cache are selectable to mount and it says "E: unable to mount '/system' "
And ADB isn't pushing anything.
Any thoughts why?
Sunset Rider said:
My buddy is having a hard time flashing a new ROM on his tablet. Currently he's running Cyanogen with TWRP.
Apparently TWRP formatted his tablet randomly and he hasn't been able to install a new ROM because his tablet won't mount the system or cache. It keeps failing. Neither system or cache are selectable to mount and it says "E: unable to mount '/system' "
And ADB isn't pushing anything.
Any thoughts why?
Click to expand...
Click to collapse
TWRP formatted his tablet randomly??? Never heard of such a thing!
And we need more information:
What versions of bootloader, CM, TWRP and you are trying to push what in ADB?
Do you have access to fastboot? What rom are you trying to flash?
What did he do - as best as he can remember?
berndblb said:
TWRP formatted his tablet randomly??? Never heard of such a thing!
And we need more information:
What versions of bootloader, CM, TWRP and you are trying to push what in ADB?
Do you have access to fastboot? What rom are you trying to flash?
What did he do - as best as he can remember?
Click to expand...
Click to collapse
It wiped his data when he went to decrypt data and it asked for a password. He hit cancel and it said system memory 0gb
He has the newest twrp, he was on 10.2 trying to go to 11, and he was trying to push the mounting through adb and was getting errors. Because he is unable to select them In twrp
He has fastboot but it doesn't respond to commands at all.
Thank you for any help
fastboot
Sunset Rider said:
It wiped his data when he went to decrypt data and it asked for a password. He hit cancel and it said system memory 0gb
He has the newest twrp, he was on 10.2 trying to go to 11, and he was trying to push the mounting through adb and was getting errors. Because he is unable to select them In twrp
He has fastboot but it doesn't respond to commands at all.
Thank you for any help
Click to expand...
Click to collapse
Sounds like a soft brick.. Due to a wrong recovery flash or he flashed the newest version of twrp, and did a full data wipe.. It has known issues!!!!!
Becareful from here.. Like berndblb said we need verify we still have fastboot access!!:fingers-crossed:
What is the OS of the PC your using to fastboot from??
Well I tried installing cromi for him and it stalls at 87%
Sunset Rider said:
Well I tried installing cromi for him and it stalls at 87%
Click to expand...
Click to collapse
UPDATE: We restarted the tablet, mid installation because it froze, and it booted up to his old 10.2 just fine. I recommended he do a clean format now but he doesn't want to do anything lol.
So right now I'm just thanking God he didn't brick it hard
Sunset Rider said:
It wiped his data when he went to decrypt data and it asked for a password. He hit cancel and it said system memory 0gb
Click to expand...
Click to collapse
Did he have the tablet encrypted or did the request for a decryption password just show up unexpectedly? If it's the latter - I have read about this a number of times - unfortunately still cannot make rhyme or reason out of it, but I suspect it's a corrupted recovery....
He has the newest twrp, he was on 10.2 trying to go to 11, and he was trying to push the mounting through adb and was getting errors. Because he is unable to select them In twrp
Click to expand...
Click to collapse
The newest meaning 2.6.3.2?
He has fastboot but it doesn't respond to commands at all.
Thank you for any help
Click to expand...
Click to collapse
Which probably means he doesn't have the correct fastboot drivers installed. That would No. 1: Get fastboot working. Download the Google Universal Naked drivers, install them and try
Code:
fastboot devices
If that returns the tablet's serial number, you're in business. You could then flash CWM 6.0.4.6 in fastboot. I would probably wipe data (hope he has everything backed up) and flash the rom.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
lj50036 said:
Sounds like a soft brick.. Due to a wrong recovery flash or he flashed the newest version of twrp, and did a full data wipe.. It has known issues!!!!!
Becareful from here.. Like berndblb said we need verify we still have fastboot access!!:fingers-crossed:
What is the OS of the PC your using to fastboot from??
Click to expand...
Click to collapse
@lj50036 could you elaborate on the issues of TWRP 2.6.3.2.? sbdags included it it in his bootloader/TWRP flash package for CROMi-X and one guy just softbricked flashing CROMi_X after flashing that package, he seems to have done everything else correctly and I suspect the recovery is buggy???
TWRP
could you elaborate on the issues of TWRP 2.6.3.2.? sbdags included it it in his bootloader/TWRP flash package for CROMi-X and one guy just softbricked flashing CROMi_X after flashing that package, he seems to have done everything else correctly and I suspect the recovery is buggy???
Click to expand...
Click to collapse
My issues are first hand.. It flashes just fine, everything seems to function correctly.. It's only the wiping of data that has a issue.... It just hangs says its doing it thing but nothing ever happens..After a hard reboot TWRP now asking for password will not mount any storage of any kind... The fastest way to a soft brick.... I posted on the TWRP forum, about the issue... Maybe we need a new forum letting people know about the issue, so we dont end up with a riot!!!
lj50036 said:
My issues are first hand.. It flashes just fine, everything seems to function correctly.. It's only the wiping of data that has a issue.... It just hangs says its doing it thing but nothing ever happens..After a hard reboot TWRP now asking for password will not mount any storage of any kind... The fastest way to a soft brick.... I posted on the TWRP forum, about the issue... Maybe we need a new forum letting people know about the issue, so we dont end up with a riot!!!
Click to expand...
Click to collapse
Thanks! Though I would love to see what a riot on XDA looks like LOL
berndblb said:
Did he have the tablet encrypted or did the request for a decryption password just show up unexpectedly? If it's the latter - I have read about this a number of times - unfortunately still cannot make rhyme or reason out of it, but I suspect it's a corrupted recovery....
The newest meaning 2.6.3.2?
Which probably means he doesn't have the correct fastboot drivers installed. That would No. 1: Get fastboot working. Download the Google Universal Naked drivers, install them and try
Code:
fastboot devices
If that returns the tablet's serial number, you're in business. You could then flash CWM 6.0.4.6 in fastboot. I would probably wipe data (hope he has everything backed up) and flash the rom.
---------- Post added at 10:18 PM ---------- Previous post was at 10:10 PM ----------
@lj50036 could you elaborate on the issues of TWRP 2.6.3.2.? sbdags included it it in his bootloader/TWRP flash package for CROMi-X and one guy just softbricked flashing CROMi_X after flashing that package, he seems to have done everything else correctly and I suspect the recovery is buggy???
Click to expand...
Click to collapse
It was version 2.6.3.0.
He had no decrypted files he was just seeing what it did when he hit decrypt data. I asked for a password which he obviously never set and hit cancel. And it said he had nothing in internal storage.
However, after the install froze on an older Cromi version I put on his sd card (from my 700t), we held down the power button and rebooted. It booted up fine to his previous Cyanogen 10.2. WITH all of his internal storage still there, EVEN THOUGH, he did a format from TWRP already.
So it's definitely a problem with TWRP. His tablet is back to the way it was before the fiasco and he is afraid to do anything else.
Sunset Rider said:
It was version 2.6.3.0.
He had no decrypted files he was just seeing what it did when he hit decrypt data. I asked for a password which he obviously never set and hit cancel. And it said he had nothing in internal storage.
However, after the install froze on an older Cromi version I put on his sd card (from my 700t), we held down the power button and rebooted. It booted up fine to his previous Cyanogen 10.2. WITH all of his internal storage still there, EVEN THOUGH, he did a format from TWRP already.
So it's definitely a problem with TWRP. His tablet is back to the way it was before the fiasco and he is afraid to do anything else.
Click to expand...
Click to collapse
Are you sure about this???
Because TWRP 2.6.3.0 was too big for the recovery partition of the TF700 and never properly installed????
For any reliable advice you need to provide the bootloader version (which you still haven't given us) and if you have a working system, you should be able to boot into recovery and give us it's version number.
For installing CM 11 on the TF700 you need to be on the 10.6.1.14.10 bootloader and have the CWM 6.0.4.6 recovery.
TWRP 2.6.3.2 supposedly works with CM 11, but I would not trust it - read about too many problems with it....
And anyway - in terms of performance, neither CM 10.2 or CM 11 beats CROMi-X on this tablet - period.
Here I am
berndblb said:
Are you sure about this???
Because TWRP 2.6.3.0 was too big for the recovery partition of the TF700 and never properly installed????
For any reliable advice you need to provide the bootloader version (which you still haven't given us) and if you have a working system, you should be able to boot into recovery and give us it's version number.
For installing CM 11 on the TF700 you need to be on the 10.6.1.14.10 bootloader and have the CWM 6.0.4.6 recovery.
TWRP 2.6.3.2 supposedly works with CM 11, but I would not trust it - read about too many problems with it....
And anyway - in terms of performance, neither CM 10.2 or CM 11 beats CROMi-X on this tablet - period.
Click to expand...
Click to collapse
Hey guys, this is Wade, the cause of the whole fiasco.
It was the newest TWRP 2.3.6.2, but I imagine it might've been a problem with the bootloader? I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2
Basically, I had tried several times that day installing CM11 and the gapps with CWM 6.0.3.1 (which ROM manager says is the up to date version? WTF?) to no avail. It kept giving me md5sum errors, and I couldn't find anything to easily fix that. CWM would also not respond to commands from ROM manager other than backups... If i told it to bootload and flash, it would just reboot normally... ADB also would fail, despite saying that i COULD connect to fastboot.
So i read on the actual CM forum that the newest TWRP 2.6.3.2 would do the trick as well, and tried that. But ya, once i booted into twrp, it threw a password query at me. I never set a password, so I pressed cancel, and that's when the partition showed up as blank.
I went to reboot, but it warned that I had no OS installed. That's about when I freaked out. It would see my microSD fine, but wasn't able to talk to /system to actually flash anything, and ADB would just give "error:closed" if I tried any mount commands there.
So ya, I invited my buddy over, and he recommended we try flashing an old CROMI-X, and it WORKED! sort of. It started to flash, even though a previous CM 10.2 and it's gapps (which I was already running and knew worked) wouldn't!
Then it froze installing Youtube, and after ten mins we held down the power.
And it booted back into CM 10.2 like nothing had happened.
Even though TWRP said I had succesfully factory reset AND wiped AND formatted the internal by that point. Lies!
So ya, I imagine it's a combination of pilot error, and TWRP being a little fluky. My question - where did that 87% CROMI-X flash go, and how can I get rid of it? And i reflashed CWM 6.0.3.1, but I'm still wary of going into the bootloader, just in case bastard TWRP is still lurkin
UPDATE
Wadesauce said:
I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2
Click to expand...
Click to collapse
So it was definitely the old ASUS 4.2 bootloader I was using. I had no idea that dasunsrule32 wanted us to use his April 2013 bootloader for 10.2 as well, the site that told me how to put CM 10.2 on my tab said to use the old ASUS one.
Finally manned up and tried my first soft reboot, and it brought up the ASUS menu with the blue loading bar - it seemed like it wanted to go into bootloader. Then it went blank and the regular ASUS logo showed, and then the CM logo and booted. So i didn't walk away from this unscathed; something low-down got messed with...
Can I update the bootloader to his, despite the problems ive been having? How do I do that?
And why does ROM manager only offer 6.0.3.1??
And since CM11 is based on 4.4, wont it eventually be better than CROMi-X?
Wadesauce said:
So it was definitely the old ASUS 4.2 bootloader I was using. I had no idea that dasunsrule32 wanted us to use his April 2013 bootloader for 10.2 as well, the site that told me how to put CM 10.2 on my tab said to use the old ASUS one.
So can I update the bootloader to his, despite the problems ive been having? How do I do that?
And why does ROM manager only offer 6.0.3.1??
And since CM11 is based on 4.4, wont it eventually be better than CROMi-X?
Click to expand...
Click to collapse
Can you still boot into fastboot mode on your tablet and can your PC see the tablet in fastboot mode?? What is the OS on your PC??
i dunno
lj50036 said:
Can you still boot into fastboot mode on your tablet and can your PC see the tablet in fastboot mode?? What is the OS on your PC??
Click to expand...
Click to collapse
I haven't tried booting into bootloader, or even a full power down/power up yet. This is the device I use for school and right now would be a pretty sh**y time for anything serious to happen to it.
I am mainly afraid that TWRP hasn't left yet, or that I won't be able to access the CWM that ROM manager says I just successfully reflashed.
I don't really want to plug it back into the computer until I know more about what happened to it. Is it likely that the CROMI that we tried flashing or the old TWRP will cause me problems? Remember that CROMI said it was 87% successful (had loaded kernel and system and all that jazz)
And I have 64 bit Win7, it should have appropriate drivers
Feedback
Wadesauce said:
I haven't tried booting into bootloader, or even a full power down/power up yet. This is the device I use for school and right now would be a pretty sh**y time for anything serious to happen to it.
I am mainly afraid that TWRP hasn't left yet, or that I won't be able to access the CWM that ROM manager says I just successfully reflashed.
I don't really want to plug it back into the computer until I know more about what happened to it. Is it likely that the CROMI that we tried flashing or the old TWRP will cause me problems? Remember that CROMI said it was 87% successful (had loaded kernel and system and all that jazz)
And I have 64 bit Win7, it should have appropriate drivers
Click to expand...
Click to collapse
Well you just let me know.. I will be here to help out if you would like it ....As always thx lj
Wadesauce said:
Hey guys, this is Wade, the cause of the whole fiasco.
It was the newest TWRP 2.3.6.2, but I imagine it might've been a problem with the bootloader? I had no idea that the bootloader needed updating; I thought that once you could boot what you wanted, that was it, but obviously I'm mistaken. Where do I find the bootloader version? It was the latest posting to the Asus download site, or the V8, 2013 bootloader edition for JB. 4.2
Basically, I had tried several times that day installing CM11 and the gapps with CWM 6.0.3.1 (which ROM manager says is the up to date version? WTF?) to no avail. It kept giving me md5sum errors, and I couldn't find anything to easily fix that. CWM would also not respond to commands from ROM manager other than backups... If i told it to bootload and flash, it would just reboot normally... ADB also would fail, despite saying that i COULD connect to fastboot.
So i read on the actual CM forum that the newest TWRP 2.6.3.2 would do the trick as well, and tried that. But ya, once i booted into twrp, it threw a password query at me. I never set a password, so I pressed cancel, and that's when the partition showed up as blank.
I went to reboot, but it warned that I had no OS installed. That's about when I freaked out. It would see my microSD fine, but wasn't able to talk to /system to actually flash anything, and ADB would just give "error:closed" if I tried any mount commands there.
So ya, I invited my buddy over, and he recommended we try flashing an old CROMI-X, and it WORKED! sort of. It started to flash, even though a previous CM 10.2 and it's gapps (which I was already running and knew worked) wouldn't!
Then it froze installing Youtube, and after ten mins we held down the power.
And it booted back into CM 10.2 like nothing had happened.
Even though TWRP said I had succesfully factory reset AND wiped AND formatted the internal by that point. Lies!
So ya, I imagine it's a combination of pilot error, and TWRP being a little fluky. My question - where did that 87% CROMI-X flash go, and how can I get rid of it? And i reflashed CWM 6.0.3.1, but I'm still wary of going into the bootloader, just in case bastard TWRP is still lurkin
Click to expand...
Click to collapse
Jeez - where to start?
First of all: Do yourself a favor and ditch ROM Manager. It does not work well with the TF700 and several people have hard bricked using it. You have been very lucky so far!
Second: Do not flash anything until you are 150% sure you know what you are doing, you understand the requirements for your situation and have everything you need at hand.
Do not flash anything EVER if you do not know what bootloader version you have. That's like getting into your car blind folded and trusting that your GPS will drive you safely to your destination.
Every ROM has it's requirements in terms of bootloader version and recovery and they are usually clearly stated in the first couple of paragraphs in the OP of the rom thread. If not: Stay away from that rom unless you know exactly what you are doing!
TWRP 2.6.3.2 has major issues when formatting data from it. Stay away from it for now.
To find out what you can do to get a stable system back, you need to know where you are and what you have.
Boot into the bootloader (and do not use ROM Manager to do it!) and read the tiny script. It'll probably be 10.6.1.14.10 or .8
Post the result.
Boot into the recovery to check what you have installed. Versions matter!
The proper way of installing a custom recovery is in fastboot mode. Which is different from ADB, btw - you've been mixing those up I think.
Google "adb fastboot tutorial" and do some reading. Once you understand, get it set up on your PC, boot the tablet into the bootloader, connect both via original USB cable and test the connection with
Code:
fastboot devices
If it returns the serial number of your tablet, you are in business and we can continue from there.
Happy studying!
Getting there...
berndblb said:
Google "adb fastboot tutorial" and do some reading. Once you understand, get it set up on your PC, boot the tablet into the bootloader, connect both via original USB cable and test the connection with
Code:
fastboot devices
If it returns the serial number of your tablet, you are in business and we can continue from there.
Happy studying!
Click to expand...
Click to collapse
Alright, I have done some reading as far as all of this goes. I understand a lot of it better now.
So I'm positive now that it was because I hadn't updated my bootloader before trying through CWM. And TWRP obviously was no more useful.
I haven't quite checked what the bootloader version is - I think there may be something wrong with it still (given my weird boot-up) and I don't want to go there until I'm totally sure what I'm doing. I'd hate to hit bootloader and then realize something was seriously wrong, and my time was ticking.
However, I have never changed the bootloader since I used ASUS's one from their website originally - since it says v8, I imagine thats the .8 one?
Before I uninstalled ROM manager, I checked what it said my recovery was - and it said I had CWM 6.0.3.1 still, even though the TWRP fiasco has just gone down. I used ROM to reflash the same 6.0.3.1 from the device, and it said it was successful.
So before I begin, could i possibly ask a few questions?
1) Could I have corrupted the bootloader?
2) Can more than one recovery exist? Is it maybe true that CWM 6.0.3.1 would be the one I will boot into if I went into recovery? I REALLY don't want it to be TWRP again as it might not survive the experience (I had put TWRP on via fastboot). Should I just get to bootloader, flash a new recovery right away and go from there?
3) When I go to finally solve it, what are the hypothetical steps I should take? Right now, as far as I can tell, it will be:
a) Make sure all drivers are working, and files (including backup) are on my PC.
b) reboot into bootloader, check version.
c) flash the 10.6.1.14.4 bootloader
d) reboot
e) reboot into bootloader
f) flash CWM. 6.0.4.6
g) reboot
i) reboot into bootloader, into recovery, then flash CM 11 and gapps
j) reboot
Ya? No? Any help would be appreciated
Wadesauce said:
Alright, I have done some reading as far as all of this goes. I understand a lot of it better now.
So I'm positive now that it was because I hadn't updated my bootloader before trying through CWM. And TWRP obviously was no more useful.
I haven't quite checked what the bootloader version is - I think there may be something wrong with it still (given my weird boot-up) and I don't want to go there until I'm totally sure what I'm doing. I'd hate to hit bootloader and then realize something was seriously wrong, and my time was ticking.
However, I have never changed the bootloader since I used ASUS's one from their website originally - since it says v8, I imagine thats the .8 one?
Before I uninstalled ROM manager, I checked what it said my recovery was - and it said I had CWM 6.0.3.1 still, even though the TWRP fiasco has just gone down. I used ROM to reflash the same 6.0.3.1 from the device, and it said it was successful.
So before I begin, could i possibly ask a few questions?
1) Could I have corrupted the bootloader?
2) Can more than one recovery exist? Is it maybe true that CWM 6.0.3.1 would be the one I will boot into if I went into recovery? I REALLY don't want it to be TWRP again as it might not survive the experience (I had put TWRP on via fastboot). Should I just get to bootloader, flash a new recovery right away and go from there?
3) When I go to finally solve it, what are the hypothetical steps I should take? Right now, as far as I can tell, it will be:
a) Make sure all drivers are working, and files (including backup) are on my PC.
b) reboot into bootloader, check version.
c) flash the 10.6.1.14.4 bootloader
d) reboot
e) reboot into bootloader
f) flash CWM. 6.0.4.6
g) reboot
i) reboot into bootloader, into recovery, then flash CM 11 and gapps
j) reboot
Ya? No? Any help would be appreciated
Click to expand...
Click to collapse
1. No, your bootloader is still good because you still can boot into your system. You need your bootloader to initiate your hardware before your OS is booting.. I am very sure that is the case but it would be nice for someone to confirm it...
2. Your recovery partition is too small for two custom recoveries to exist. So it is almost impossible for you to have two recoveries..
Before you want to go further, it is easier to find out your bootloader and recovery versions so you know what is the next step that you need to do. Otherwise, it is just a guess or a shot in the dark... I think that you are fine but you need to wait for some experts to confirm it... Good luck...:fingers-crossed:
Please bear with me
LetMeKnow said:
Before you want to go further, it is easier to find out your bootloader and recovery versions so you know what is the next step that you need to do. Otherwise, it is just a guess or a shot in the dark... I think that you are fine but you need to wait for some experts to confirm it... Good luck...:fingers-crossed:
Click to expand...
Click to collapse
Sorry hahah, I know I must seem really frustrating...
I have held off for 2 reasons:
1. The first time I did a soft reboot after my fiasco, upon boot it went through the first series of steps trying to load into the bootloader, but then booted fine. Another time a few days after, it rebooted while i was using it, and just went blank after the asus logo. Holding the power down caused it to boot fine. Still, neither of those had ever happened before, and I am pretty sure that some point along the line of bootloader-->OS something is broken. Hopefully on the OS side.
2. I am not going to attempt to boot into recovery until I know that it isn't the same TWRP 2.6.3.2 that got me into this whole fiasco. I know it sounds like a catch 22, not wanting to reboot into recovery to check what it is, but I have NO IDEA how to get out of this TWRP as it stands. I had to flash a CROMI (which failed at 87%) and hard reboot. Not willing to go out on a limb and assume that hard-reboot will work during any step of that process.
So, why do I have to check it? Can't I boot into bootloader, flash a new bootloader, flash a new recovery, and then reboot normally? Assuming I'll be able to establish fastboot (drivers still work, so fingers crossed on that one).
So I've been running rooted stock for a while and decided to try out blisspop. After a few days I decided to return to stock, partly because I read about the 3.1.1 update coming out. I downloaded the 3.1 full OTA, flashed it with TWRP and all was fine. Things started to get wonky when I got home the other night and decided to update the controller( I hadn't done it after the 3.1 update rolled out). The controller wouldn't update and the tablet kept freezing up. Then the download for the 3.1.1 update showed up and of course I didn't flash it because I wasn't stock. Then I started getting google play services errors and I couldn't do a thing so I did a factory reset. During the setup process it keeps freezing up during 'Checking connection'. I can forget the network, go through the setup and get to the home screen but then I have no icons. I can restart the tablet and the the default icons appear where I can then connect to my wifi network but I can't add a google account(keep getting google services errors)(I enter my email address to add the account, hit 'next' and it freezes up). The weird things is this even happens when I reboot to bootloader and
fastboot erase system
fastboot erase userdata
fastboot erase boot
fastboot erase recovery
fastboot erase cache
and then
fastboot flash recovery {dir}/recovery.img
fastboot flash boot {dir}/boot.img
fastboot flash system {dir}/system.img
fastboot flash userdata {dir}/userdata.img
fastboot flash staging {dir}/blob
fastboot flash dtb {dir}/tegra124-tn8-p1761-1270-a04-e-battery.dtb
This is of course after downloading the recovery image(3.1 found here http://forum.xda-developers.com/shield-tablet/general/stock-recovery-images-ota-library-guides-t2988881) and verifying the md5 so I know everything is good. The really wierd thing is, I have none of these problems if I get back into the bootloader, flash TWRP, reboot into recovery and then flash bliss, gapps, and reboot.
Does this make sense to anyone?
Any help would be appreciated
Thanks
Update: I went through the same process and flashed the stock 2.2.2 recovery image. Same results, I cannot add a google account but I can connect to my wifi network. Right now it's downloading the 3.1.1 update, so we'll see in a bit.
deleted
All is good. I still have no idea what I screwed up.
After using the fastboot erase commands, and then flashing TWRP, I noticed some messages in twrp about not being able to mount /system, /data, etc. So who knows? So I tried to flash blisspop again and I ended up in a loop booting into twrp again and again.
So I erased everything again, flashed twrp, booted to recovery and formatted internal storage. I flashed the full 3.1.1 OTA, rebooted and my world is beautiful again(no google play services errors).
Hopefully these posts help someone, if some sense can be made of them.
Sent from my SHIELD Tablet using Tapatalk
Man this helped me out tremendously!!! I think just the steps to manually erase each partition (if thats what they're called) is what ended up helping me. I had to do it twice for it to work properly but it worked! And I'm pretty sure I tried everything the past few days. I wasn't having the same problem as you. My tablet was stuck on the nvidia boot screen after trying to flash stock recovery. Thought I bricked my device for a couple days. Thanks for posting!
unable to flash any update with twrp..need help.. with each ota file the error comes-- " package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K... this device has nvidia/omni_shieldtablet/shieldtablet:6.0.1/MOB30D/ "
manish.kumar86 said:
unable to flash any update with twrp..need help.. with each ota file the error comes-- " package expects build fingerprint of nvidia/sb_na_wf/shieldtablet:6.0.1/MRA58K... this device has nvidia/omni_shieldtablet/shieldtablet:6.0.1/MOB30D/ "
Click to expand...
Click to collapse
Please try to ask in only one place, it's confusing to those who try to help you when the same question is in the different posts
Sent from my SHIELD Tablet K1 using Tapatalk
I know but no solution from anywhere.. now i have even stuck in worse situation. Tries flashing all three version of stock image--
SHIELD TABLET K1 open source and binary driver release for OTA 1.2.0
SHIELD TABLET K1 open source and binary driver release for OTA 1.1.1
SHIELD TABLET K1 open source and binary driver release for preinstalled factory image
but not able to boot into recovery and also its not booting for hours.. i feel i cant revert from android 6.0.1 to any one of the stock image given by nvidia mentioned above..
Even tried experimental twrp and any other twrp i can find for shield k1, but its not going into recovery..
any help wd be great..
Exile1975 said:
Please try to ask in only one place, it's confusing to those who try to help you when the same question is in the different posts
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
where is this battery.dtb file? its not in the folder i downloaded from nvidia and i cant find it anywhere
oilerseberle14 said:
where is this battery.dtb file? its not in the folder i downloaded from nvidia and i cant find it anywhere
Click to expand...
Click to collapse
Me neither
Just got my XT1644 G4 Plus 16GB here in America and brought it home for some testing.
Everything was a piece of cake, I did these things in order with no issues. There are other guides for these things all over XDA so I won't be giving detailed instructions.
Unlocked the bootloader here - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Installed TWRP from here. - http://forum.xda-developers.com/mot...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
And flashed SuperSU from here - https://download.chainfire.eu/696/supersu/
When TWRP first boots it will ask if you want to run in systemless mode. Make sure you tell it YES!!!
Rebooted on the first try with no issues.
I have Xposed installed with a few modules and it works great.
Sent from my Moto G (4) using Tapatalk
Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.
mystx2112 said:
Can anyone get me a stock boot.img i seemed to have messed up my adb protocol on the phone and my computer will no longer allow it to give me an RSA key prompt. The method worked for me though.
Click to expand...
Click to collapse
Can extract it from the stock ROM here: https://www.androidfilehost.com/?fid=24572369242687085
not sure if this is full proof i got bootloop
After flashing SuperSu 2.76 the phone is stuck forever at the "moto" logo. Is it because I'm using such a new version of SuperSu? Why do you use 2.46?
How long did it take to get the unlock code? I am waiting for a couple hours now...
LE: 4 hours... and finally I got the code.
Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.
craigl14 said:
Just got XT1644.
Unlocked bootloader with no problem.
Installed TWRP 3.0.2-0 with no problem
Installed SuperSu 2.46 in read only mode.
Stuck at moto screen.
Any help would be appreciated.
Click to expand...
Click to collapse
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.
I can't get twrp to install. I keep getting told that the image is not signed or corrupt
First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.
SoNic67 said:
First unlock Bootloader.
You don't need to install TWRP, just boot into it so you can flash the Systemless SuperSU.
Click to expand...
Click to collapse
that's just it... I can't boot to twrp. It's not there.
Where? You can't find it on the SD by browsing in the recovery?
because that's just it, there's nothing in recovery. This has gotten so convoluted that I don't even know what I'm supposed to have where....
@davidkoby
Stock ROM Recovery starts with a "Dead Android" and "no command" written under it, it is you see or something else?
Does supersu need to be in systemless mode?
craigl14 said:
Nevermind. Followed steps 5-8 of this post http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 and all is well.
Click to expand...
Click to collapse
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.
sam9s said:
Hi Bro,
I was also stuck at the moto logo screen and then I followed steps from 5-8, (where I see the superSu file is of different version), and now my phone is not booting at all, normally. I can boot in to bootloader but not normal boot is happening, I cannot even switch on my phone. I am a bit scared. Can you please assist.
Click to expand...
Click to collapse
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.
craigl14 said:
Assuming you have XT1644, stock marshmallow ROM and TWRP recovery installed, maybe boot into recovery and double check that the .supersu file you created is in the data directory (step 6) through file manager. If it's there maybe flash the supersu zip file in OP since that is the version that worked for me. If neither works maybe factory reset in recovery and flash the correct supersu zip and try again. Failing all that, you may have to completely start over and reflash the ROM. My guess is creating the .supersu file wasn't done correctly or the incorrect version of the supersu zip is causing the problem.
Click to expand...
Click to collapse
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy
sam9s said:
Ok yes I have XT1644 (any way to confirm BTW), I also have TWRP recovery installed (thats how I took the backup)m BUT, I was not on stock marshmallow, I was on nougat (Stock), The phone did an OTA update, months ago. Could that be the reason.
Also I checked .supersu file was there via file manager. What do you advice ..??? I also have tried now with SR3-SuperSU v2.79, but same result, it get stuck at Moto Boot screen.
Another thing I noticed at the screen where it says "Your phone is unlocked and cant be trusted" and it will boot in 5 seconds, in front of ID it says BAD KEY ... wonder what that means or if it has something to do with what wrong has happened.
Appreciate your assistance here.
Regards
Sammy
Click to expand...
Click to collapse
Hmmmm...I don't know if you have XT1644. Most who have that version are still waiting on OTA I think and certainly didn't get it month's ago. It is the G4 Plus North American version. If you still have the box it will be on the UPC label. It will also be in your phone info in settings once your phone works again. Did your phone work fine before you tried to root it? Anyway, Nougat will not root with this method. If you can boot into recovery, try factory reset. If that doesn't work, you're going to have to reflash the Nougat ROM...make sure you get the right one for your phone. You will need to search around on this forum for instructions and which download to get, etc. Once you have Nougat up and running again, you will need to leave it unrooted or use one of the proven methods of root. Again, I don't think systemless supersu works for Nougat. I have no idea what bad key means. The only thing I've ever had is "N/A" come up in the unlock warning. Incidentally, you can get rid of the bootloader warning screen if you want to.
Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John
Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.
Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John
Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.
Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.
firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
[email protected] said:
I wanna start by saying that I tried all kinds of Googling and searching this site, and kept finding answers that are really close to my question, but not.
So I got my old Nexus 6P out, unlocked the bootloader (did that years ago for some reason but don't recall why), installed TWRP, formatted, installed stock image from Google Devs or whatever, installed TWRP again, rooted, installed SuperSU, Termux, TWRP app, and a few others to make sure that I have root (I have root), and everything was cool up to that point.
I used TWRP to make a backup at that point, flashed the NetHunter zip for my phone (Nexus 6P Angler), and now it won't boot the OS. It will stop at the bootloader. TWRP recovery still works.
When flashing the NetHunter ZIP, I got success messages. For giggles, I tried installing the NetHunter ZIP twice in a row, and the status messages indicated that it detected some components were already there, so it seems like it is installing, but just not booting.
If this were a computer, I would see if the boot config or partitions needed adjustment, but I'm not sure how to do this from TWRP.
Also, I have the phone in dev mode, usb debug mode, and have ADB and FASTBOOT installed on my computer (Linux Mint something from 2019 or 2020) and all the hardware IDs for FASTBOOT installed and both ADB and FASTBOOT seem to be working perfectly.
When I restore the backup, it takes me back to a working phone, sans NetHunter.
I really want the full install to take advantage of the custom kernel that a allows for WiFi and USB stuff.
I'm sure I'm making at least one silly mistake. Any help would be wonderful!
Click to expand...
Click to collapse
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
I formatted, installed factory image, installed TWRP, flashed Magisk, confirmed root, flashed NetHunter ZIP, same result
Droidriven said:
Get rid of SuperSU and use Magisk root instead. SuperSU is old news and no longer supported. Magisk is the current and most reliable rooting method these days.
Flash the stock image, install TWRP, then flash the Magisk.zip and you'll be rooted. Then continue from there.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
So if anyone else is facing the same issuing of wanting to install this old(ish) software onto this old(ish) hardware, and got stuck in the same place as me, here are the three steps that I had to take to succeed that were not in official documentation:
1)When flashing the factory Android image, make sure that you are using the newest version that is supported by NetHunter. At time of writing, this is not the same as the newest version of Android.
2)Remove the -w option from the installation script
3)Be sure to install a compatible kernel from builds.nethunter.com
Thanks again to @Droidriven for the tip on using Magisk