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).
I think I screwed up big time....
I just got my M8 (came from an M7) and I am def S-OFF (checked in bootloader). I have TWRP and when I try to install any ROM, it starts ok first but then it ends with symlinks failed. When I hit reboot, it goes back into recovery. I think I might now the issue and I think it is because I did not delete weaksauce ... I just installed TWRP and rebooted and everything was deleted so I have the custom ROM on the external SD card. I can't even do sideload because it won't find it (when I do adb devices it shows list of devices found but it's empty .. no number like it should be). I fudged up, I know....not sure if it is the weaksauce issue but I'm grateful for any help
UPDATE 1
I have switched to CWM and looks like sideload now works...I'm just installing a ROM and hopefully it'll work. If not, would anybody suggest this...
http://forum.xda-developers.com/showthread.php?t=2727831
the whole RUU flash....either option 1 (if it works) or option 2? If I'm understanding it right, this will wipe everything and go back to stock completely ... then I can do it all over and not screw up...
UPDATE 2
Got it to work....just for those who may have had the same issue. After switching to CWM, sideload did not work. I placed the ROM on an external SD and flashed it as usual and this time it worked (it did not on TWRP for some reason).
?
ghilliek9 said:
I think I screwed up big time....
I just got my M8 (came from an M7) and I am def S-OFF (checked in bootloader). I have TWRP and when I try to install any ROM, it starts ok first but then it ends with symlinks failed. When I hit reboot, it goes back into recovery. I think I might now the issue and I think it is because I did not delete weaksauce ... I just installed TWRP and rebooted and everything was deleted so I have the custom ROM on the external SD card. I can't even do sideload because it won't find it (when I do adb devices it shows list of devices found but it's empty .. no number like it should be). I fudged up, I know....not sure if it is the weaksauce issue but I'm grateful for any help
UPDATE 1
I have switched to CWM and looks like sideload now works...I'm just installing a ROM and hopefully it'll work. If not, would anybody suggest this...
http://forum.xda-developers.com/showthread.php?t=2727831
the whole RUU flash....either option 1 (if it works) or option 2? If I'm understanding it right, this will wipe everything and go back to stock completely ... then I can do it all over and not screw up...
UPDATE 2
Got it to work....just for those who may have had the same issue. After switching to CWM, sideload did not work. I placed the ROM on an external SD and flashed it as usual and this time it worked (it did not on TWRP for some reason).
Click to expand...
Click to collapse
in update 2 how did you flash??
@SidDev said:
in update 2 how did you flash??
Click to expand...
Click to collapse
you will have to download CWM ...put it on your computer in your adb folder....put your phone into fastboot then on your computer you have to fastboot flash recovery (and then the name of the CWM version) and that is it. Now you have CWM ...
oh ok
ghilliek9 said:
you will have to download CWM ...put it on your computer in your adb folder....put your phone into fastboot then on your computer you have to fastboot flash recovery (and then the name of the CWM version) and that is it. Now you have CWM ...
Click to expand...
Click to collapse
I was trying to gain knowledge,
BTW I have moto e with twrp
---------- Post added at 10:42 AM ---------- Previous post was at 10:37 AM ----------
ghilliek9 said:
you will have to download CWM ...put it on your computer in your adb folder....put your phone into fastboot then on your computer you have to fastboot flash recovery (and then the name of the CWM version) and that is it. Now you have CWM ...
Click to expand...
Click to collapse
I was trying to gain knowledge,
BTW I have moto e with twrp
Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Omg i forgot that the bootloader might be locked.. Ill try to find the comand to put my unlock code in and get back to this thread.. Thanks so much for suggestions.. Though ive had tkbdeal with it nougat is FANTASTIC
UPDATE: So far nothing is working. Tried the rollback packages and im still on nougat. I have an actual firmware version now. But its Russian firmware? Trying the dload method with L29185 firmwares like 200 and 320 and nothing works. Tried many things and now i cannot even install twrp. The install process would work it just wouldnt do anything when i tried to boot to twrp but now when i try to flash twrp over the recovery it just completely fails. no error code it just says it cannot find a file by that name or it cannot read it. adb says the bootloader is unlocked. Am i just completely stuck here on a buggy nougat installation? Is there any way to force a twrp backup to load outside of twrp?
gm007 said:
First you need to roll back to ur previous firmware.
You can try dload method using ur previous firmware or use rollback package.http://forum.xda-developers.com/mate-8/general/best-easiest-to-rollback-to-emui-4-0-t3507399/page1
When ur back with a working firmware,you have to unlock bootloader if its locked again,and flash twrp.
Once done u have to download nougat firmware with the data zip ment for ur region.
Go to twrp install the 2 zips( firmware and data) than reboot.
If the phone didn't boot after 10 minutes ,reboot into recovery( twrp will be replaced with stock recovery after installing the zips) and do factory reset.
Click to expand...
Click to collapse
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
OcazPrime said:
ok so now most of this is done. Excuse me for pulling you aside I do hope you reply. Im having an issue getting twrp to work. Im on an official stock firmware. Bootloader unlocked, flashed twrp and im stuck at the screen that says my device cannot be trusted. Its on its way to booting to twrp but it completely wont. Its just stuck at that screen for about 5 minutes now. Ive let it ride and i think its just frozen there. Any ideas? im using the twrp posted by the commenter above you. The 3.0.2-1 and this is where im at.
Click to expand...
Click to collapse
That twrp is for mate 9 and will not work for mate 8 you need to fastboot another twrp. You need to flash another twrp you can try the twrp for the honor 8 which will work on mate 8
http://forum.xda-developers.com/honor-8/how-to/twrp-nougat-edition-t3504140
You will be to get into this twrp but not all functions are working.
---------- Post added at 02:03 AM ---------- Previous post was at 01:59 AM ----------
OcazPrime said:
Well now i cannot get my phone to stop wanting to factory reset itself. It keeps trying to boot into recovery and twrp is flashed over stock recovery and twrp still wont boot even though bootloader is unlocked. it freezes at the unsafe device booting screen every time it starts. I think this phone is bricked beyond repair now. Nougat update completely ruined my phone.
Click to expand...
Click to collapse
As long as you can get into fastboot mode, you can recover. Try to flash the nougat stock recovery then use the rollback package (try all three to see which one work) then you can dload back to your previous rom.
---------- Post added at 02:06 AM ---------- Previous post was at 02:03 AM ----------
Icchan said:
have you tried to flash through fastboot the twrp in this thread? http://forum.xda-developers.com/mate-9/development/recovery-unofficial-twrp-huawei-mate-9-t3515617 (do not worry if is for mate 9. it works anyway)
also please check if your bootloader is unlocked before doing it.
download srk huawei tool, is pretty easy to use: http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Click to expand...
Click to collapse
Did you try it and it works for you? I flashed this twrp and my phone just get stuck at the screen "your phone is booting" and I have to flash another twrp.
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
OcazPrime said:
In total what ive done up to my current state:
Flashed nougat in. Installed wrong tried reverting and noticed twrp wouldnt boot. Downloaded rollback packages. Only the russian one worked and ended up on C636B180 firmware. Checked my other recovery thread for twrp and got twrp working finally. TWRP wont flash any roms for some reason. When it flashes roms it doesnt actually install anything. When i boot it just sits there on the screen you get with an unlocked bootloader i havent let it sit there for long because when i get back into twrp and check the file manager, there are no files in sdcard. So my rom straight up didnt install. When i check it on my pc the storage size hasnt decreased at all. Its just completely screwed right now and im so frustrated im probably getting a new phone.
Click to expand...
Click to collapse
If you are back to C636B180 firmware, you need to unlock the phone, flash twrp, which is fully working in emui 4, root the phone then use SRK to change to the software region you want:
http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
Can i just download a superuser zip and flash it with twrp to root? Havemt rooted this phone in forever cuz i never did much with it since my first and only rooting
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
LastStandingDroid said:
The reason why recovery doesn't work is due to kernel isn't supported on new bootloader
Click to expand...
Click to collapse
What?
The previous twrp version doesn't work on nougat due to kernel.
I guess it's selected by bootloader or the new teecd
You can download twrp as mentioned here
http://forum.xda-developers.com/showthread.php?p=70126187
Also @tknguyencsu what works in that version for your mate 8?
Does MTP work and adb?
Data won't work unless you use encrypted version.
Sent from my FRD-L09 using Tapatalk
OcazPrime said:
Ive tried to install TWRP via adb about 3 times now and it just will not work. The install goes perfectly but when i try to enter recovery mode from the phone being turned off, it just infinitely says my phone is booting. Does not go into twrp at all. My Nougat installation is extremely buggy. I have no model number, i went through complete hell to even enter my google account info. Everything seems to work fine on nougat though but i just cannot stand the bugged installation. Could really use some help.....
EDIT: Flashed TWRP through adb sideload and the phone just sits there still even when i enabled usb debugging and all. Bluetooth doesnt work and NFC doesnt work. But everything else works perfectly fine. It would just be nice to get the full functionality of my phone back. Phone isnt rooted. Just need some quick assistance.... Thanks for whomever answers.
United States user
Huawei NXT-L29
Android 7.0
Click to expand...
Click to collapse
Budy I have same problem Pls note me when u find somethıng :=)) ıf I then ı will let u know.
TWRP Recovery 3.0.3
Download TWRP Recovery 3.0.3
http://sillanwali.com/downloads/twp-3.0.3.img
Hi,
It has been a while since ive dealt with custom roms and im wondering if im forgetting something, what im experiencing is that no matter which linageOS rom i install i get stuck for hours on end on the linageOS booting screen. Ive been wondering if theres something like a verbose boot that could show me what is happening when booting. What ive been doing is Install the rom (wipve dev/cache) then install gapps (nano or full) then wipe dev/cahce and still getting the same result every single time.
Now i dont know how to proceed from here, my conclusion is either im doing something completely wrong or this device is not compatible with the 8013 roms however it says 801X all the files say 8013 after youve downloaded them. If another brain could shed some light on this that would be greatly appreciated
Greetings,
Jules
Firgured out my issue it was due to having TWRP 2.8 instead of 3.0, somehow TWRP cant flash it properly on version 3.
I'm havng the same problem, or was. For me too it has been awhile! I was able to boot finally by following these steps:
1. advanced wipe, everything but my ext sd card
2. install os rom zip
3. install gapps zip
4. reboot by selecting do NOT install supersu root or whatever it offered
Now though I'm in and can't download chrome though the play store so I'm about to reflash the stock rom gapps rather than the pico gapps.
just saw your reply - strange as i'm using 2.8 and can't figure out how to update my twrp as fastboot totally freezes
TWRP see twrp thread in development .
or twrp.me
Updates via zip or tar file .
Fastboot on Note 10 ??
JJEgan said:
TWRP see twrp thread in development .
or twrp.me
Updates via zip or tar file .
Fastboot on Note 10 ??
Click to expand...
Click to collapse
@JJEgan when you say twrp updates via zip or tar, is this an automatic update? i also cannot seem to get past the lineage boot screen so not sure how to update it unless i can just drop it on the sd card.
No you update the file via Odin or TWRP .
twrp.me
JJEgan said:
No you update the file via Odin or TWRP .
twrp.me
Click to expand...
Click to collapse
Thanks. @JJEgan I was hoping you might be able to advise on my issue?
I have twrp 2.8 installed from when Blisspop was installed in 2015. It allowed me to wipe and proceed.
Using twrp i then installed Lineage lineage-14.1-20181103-TESTING-n8013, addonsu-14.1-arm-signed and open_gapps-arm-7.1-stock-20190403. These are the things I was able to make a guess that I needed based on reading here.
Problem: stuck at Lineage's logo boot screen
Mistakes I think I made from further reading:
- twrp 3.0 should be used to install ROM
- smaller gapps suite (nano) should be used
Obstacles:
- I can boot the 8013 to Odin Screen. I have Odin running on Windows 10. I have the driver for the 8013 installed in Windows that allowed me to drop the Rom and stuff onto the SD card. However, when I boot into Odin, nothing happens in Odin in Windows.
- Not sure what version of TWRP is really apporpriate
And overall, I'm just guessing about all of this. I understand "the answers are here" but there are millions of answers and I'm having problems deciphering which ones are correct.
Thank you so much. I would be most appreciative if you could point me to the correct twrp for the GT-N8013 and a guide to how to install it via Odin when TWRP is already present and if my other research is correct.
Either update through TWRP as twrp image or via Odin as TAR file .
<However, when I boot into Odin, nothing happens in Odin in Windows. >
You open Odin on windows put tar file in correct slot .
Boot to Download mode on tablet then connect usb cable
Odin press start.
https://forum.xda-developers.com/showthread.php?t=2080366
JJEgan said:
Either update through TWRP as twrp image or via Odin as TAR file .
<However, when I boot into Odin, nothing happens in Odin in Windows. >
You open Odin on windows put tar file in correct slot .
Boot to Download mode on tablet then connect usb cable
Odin press start.
https://forum.xda-developers.com/showthread.php?t=2080366
Click to expand...
Click to collapse
Thank you angel aka @JJEgan! I will try this when I get home from work.