Related
Sorry, for bothering you with this but unfortunately, I have soft-bricked my phone. It's a WIND Canada HTC One S with S4 cpu, CID is GLOBA001 with HBOOT 1.14.0004.
I had Cyanogenmod 10 installed, ran in some problems, tried to find a solution (among others this: http://forum.xda-developers.com/showthread.php?t=1630459 didn't work) and bricked it: boot loop, unmountable /sdcard, no working recovery. I have tried for hours all the tips I found in the forums but none helped. I even downloaded a RUU but I couldn't install it (probably the wrong version).
Current state is: I can only get into the bootloader which is re-locked (by courtesy of one of my repair attempts). Connecting via USB to fastboot works. Nothing else, for all purposes the phone is clean, empty and oh so very much dead.
How do I proceed from here? In the end I want to have working version of Cyanogenmod back.
Thank you in advance, guys!
el_Harmakhis said:
Sorry, for bothering you with this but unfortunately, I have soft-bricked my phone. It's a WIND Canada HTC One S with S4 cpu, CID is GLOBA001 with HBOOT 1.14.0004.
I had Cyanogenmod 10 installed, ran in some problems, tried to find a solution (among others this: http://forum.xda-developers.com/showthread.php?t=1630459 didn't work) and bricked it: boot loop, unmountable /sdcard, no working recovery. I have tried for hours all the tips I found in the forums but none helped. I even downloaded a RUU but I couldn't install it (probably the wrong version).
Current state is: I can only get into the bootloader which is re-locked (by courtesy of one of my repair attempts). Connecting via USB to fastboot works. Nothing else, for all purposes the phone is clean, empty and oh so very much dead.
How do I proceed from here? In the end I want to have working version of Cyanogenmod back.
Thank you in advance, guys!
Click to expand...
Click to collapse
Unlock it first, you can't do anything with it locked.
Darknites said:
Unlock it first, you can't do anything with it locked.
Click to expand...
Click to collapse
Okay, the device is unlocked again. How do I continue?
Thanks a lot, by the way!
el_Harmakhis said:
Okay, the device is unlocked again. How do I continue?
Thanks a lot, by the way!
Click to expand...
Click to collapse
Flash TWRP recovery and try to mount the sd and connect it to the pc.
Darknites said:
Flash TWRP recovery and try to mount the sd and connect it to the pc.
Click to expand...
Click to collapse
Okay, flashing TWRP worked. I then booted into recovery, clicked on "mount" and then "mount usb device". After some driver installs I can no see the internal storage. Apart from a folder for TWRP and .android_secure it's empty. Is this where I now put the Cyanogenmod file and install it via the recovery?
el_Harmakhis said:
Okay, flashing TWRP worked. I then booted into recovery, clicked on "mount" and then "mount usb device". After some driver installs I can no see the internal storage. Apart from a folder for TWRP and .android_secure it's empty. Is this where I now put the Cyanogenmod file and install it via the recovery?
Click to expand...
Click to collapse
Ya place it where you want and then flash it but you will need to fastboot the boot.img file thats in the rom zip, you can use the All-In-One Toolkit to do that.
Darknites said:
Ya place it where you want and then flash it but you will need to fastboot the boot.img file thats in the rom zip, you can use the All-In-One Toolkit to do that.
Click to expand...
Click to collapse
Copying the ROM and then installing via TWRP worked though I saw that TWRP displayed an error, saying it was unable to mount /cache. When I tried to wipe the Cache & Dalvik Cache I got the same error.
Nevertheless I then went ahead and copyed the boot.img (extracted that one from the Cyanogenmod zip) via fastboot and rebooted the device. Now the phone is stuck in the Cyanogenmod boot loop.
el_Harmakhis said:
Copying the ROM and then installing via TWRP worked though I saw that TWRP displayed an error, saying it was unable to mount /cache. When I tried to wipe the Cache & Dalvik Cache I got the same error.
Nevertheless I then went ahead and copyed the boot.img (extracted that one from the Cyanogenmod zip) via fastboot and rebooted the device. Now the phone is stuck in the Cyanogenmod boot loop.
Click to expand...
Click to collapse
Hmm think you going to have flash the stock recovery then do a factory reset in the bootloader then go back to TWRP and copy over the rom again then factory reset in TWRP and then wipe system and then flash the rom. Do not lock the bootloader.
Darknites said:
Hmm think you going to have flash the stock recovery then do a factory reset in the bootloader then go back to TWRP and copy over the rom again then factory reset in TWRP and then wipe system and then flash the rom. Do not lock the bootloader.
Click to expand...
Click to collapse
Okay, I will try that! Where might I get the stock recovery? I don't want to pick the wrong!
el_Harmakhis said:
Okay, I will try that! Where might I get the stock recovery? I don't want to pick the wrong!
Click to expand...
Click to collapse
Go here for it.
Darknites said:
Go here for it.
Click to expand...
Click to collapse
Ha! It finally worked! Thank you very much! Have a nice weekend!
el_Harmakhis said:
Ha! It finally worked! Thank you very much! Have a nice weekend!
Click to expand...
Click to collapse
Np dude, you too.
Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, is used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.
You have flashed the latest TWRP via fastboot and it still wont flash roms? Also, what bootloader are you on?
Sent from my ASUS Transformer Pad TF700T Infinity using Tapatalk HD
Rom: CleanRom 3.4.4
Phultara said:
Alright, so, my tablet decided to one day just cease stop working. The recovery for some reason can't flash anything now, it used to be able to flash a backup, but not anymore. It used to be able to boot past the animation, but not anymore. I cannot flash a ROM from recovery because it says that the file is bad (and please, don't tell me to check to see if the md5's are correct, they are, I've triple checked.) I've flashed CWM recovery and TWRP recovery, and TWRP cannot fix permissions, but CWM recovery can, but neither can flash a single ROM. I've tried sideloading a rom but i get this error from the CMD window
Code:
* failed to write data 'protocol fault (no status)' *
. I'm at my wits end here. The bootloader is perfectly fine, it works 100% but I can't flash a single thing from recovery. I've flashed non-corrupted recoveries, and still I cannot flash a thing.
Click to expand...
Click to collapse
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.
Thats OK said:
What tablet do you have?
From where did you download which recovery for which Asus tablet.
Sounds like the recovery version doesn't match the device.
Click to expand...
Click to collapse
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped
Phultara said:
Asus Tf700 32 GB. I got the recovery from the TWRP website. In answer to the boot loader question, I have no idea how to check. All I know is that I can choose between RCK, Cold Boot, Fast boot and Wipe Data.
Click to expand...
Click to collapse
If you have the 4 icons that indicates JB.
Sounds like the custom recovery is not installed if your on the RCK icon and press the up volume rocker and nothing happens.
adelancker said:
Have you ever unlocked the bootloader? (If not: do so by searching on Asus' site for the Unlock Bootloader Tool v7) It's a simple apk which you install and then check and let it unlock.
Only then, you can start flashing!
If you already have unlocked, maybe you sent it in (?) Or flashed an official Asus rom (?), you might want to unlock it again.
Let us know if any of these answers above helped
Click to expand...
Click to collapse
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Phultara said:
When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
Can you get adb shell access to your recovery?
Which ZIP are you actually trying to flash? What is the exact error message from the recovery? Try running md5sum (inside the adb shell) on the file you want to flash. Check the output of "mount". Check if /cache/recovery/log contains interesting info.
Phultara said:
Unlocking it would require an OS to be installed, but none is installed because I was wiping to install a different ROM. I have unlocked it. In response to the boot loader, yes, it has 4 icons. So I guess it is the JB boot loader. When I go to RCK it does boot recovery but from there on its unable to open any zips besides any backups I have. When I reload a backup it doesn't install the OS, but it restores everything else.
Click to expand...
Click to collapse
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?
adelancker said:
AH sorry!
I only read the title and replied lol
Does adb do anything?
Or is adb not working either?
Click to expand...
Click to collapse
How would I go about connecting through ADB?
Phultara said:
How would I go about connecting through ADB?
Click to expand...
Click to collapse
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".
_that said:
* Connect your tablet to a computer with proper drivers and adb installed.
* Boot tablet to recovery.
* On computer, type "adb shell".
Click to expand...
Click to collapse
Alright, I'll have to try that when I get home in about 3-4 hours. I'll get back to you on that. Also, I noticed last night that when I was on fast boot, it would stay stuck as waiting for device on the cmd window. I'm not sure if it was my computer that didn't detect it or a new symptom. O hope its just a fluke!
Alright, here's the log from my recovery.
Phultara said:
Alright, here's the log from my recovery.
Click to expand...
Click to collapse
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.
buhohitr said:
OK, I assumed that you're not using data2sd. 1. Make sure your microsdcard is good (reformat and recopy your backup or rom if needed),2. Boot into twrp and wipe cache, dalvik cache, factory reset, wipe system, wipe internal then finally the most important part, FORMAT SDCARD. Now reflash a new rom or try to restore from backup. I would try step#2 first. Good luck.
EDIT: format sdcard instead of wipe sdcard.
Click to expand...
Click to collapse
That did it!!! Thank you!!!! Looks like it was the SD that was the root of the issue! Thanks!!
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 unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
ma_moto said:
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
Click to expand...
Click to collapse
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
enaon said:
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
Click to expand...
Click to collapse
So you just flashed CM11, even though it booted back into stock recovery ?
ma_moto said:
So you just flashed CM11, even though it booted back into stock recovery ?
Click to expand...
Click to collapse
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
enaon said:
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
Click to expand...
Click to collapse
I did pretty much the same thing right now and just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
ma_moto said:
I did pretty much the same thing right now just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
Click to expand...
Click to collapse
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
enaon said:
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
Click to expand...
Click to collapse
I used CWM directly from their site, maybe that's why it isn't working probably.
You're right i should do a clean reflash, but I'm getting sick of constantly reinstalling and configuring everything
I know there is another very similar thread that was just opened(http://forum.xda-developers.com/oneplus-one/help/completely-stock-oneplus-one-stuck-t3396207), but his solution didn't help me so I'm making this thread.
I really need to save my internal data, so only as a last resort will I wipe userdata to save my phone.
First of all my phone is completely stock. Locked bootloader, unrooted, stock recovery, and stock rom. Last thursday(June 9th), I got the CM13.1 OTA update which I installed and everything went normal. It finished installing, restarted and booted up, optimized apps, rebooted, but then optimized apps again and again. I thought it might help to just reboot my phone, but it didn't. So I immediately started looking around for solutions.
I can boot into recovery and fastboot mode and since I can boot into recovery I started with wiping cache(Stock Recovery>>Factory reset>>Wipe cache partition). It took ~20mins which seemed like an unusually long time, then I rebooted and it still got stuck in the "optimizing apps/reboot loop". Next, I set up USB drivers, ADB, and fastboot since it seems to be very important to have those set up. I used a few guides to get them properly set up and I checked that they were correct by checking that the cmds "adb devices" and "fastboot devices" returned my device, which they did. I saw someone saying he saved his friends OPO by just ADB sideloading a CM zip file, so it looked hopeful in my case. I downloaded cm 13.0 and 13.1 zip files and tried sideloading them with the cmd "adb sideload cm13.zip". I tried both and they both got to around 50% complete and the install failed. Some of the red text said, "Package expects build fingerprint of oneplus/bacon/A0001:5.1:6.0.1..... & E:Failed to install /sideload/packages.zip ". Next I tried installing TWRP, which looks like it requires an unlocked bootloader to flash it(even to to just boot into it). From all my research it looks like there's no way to unlock the bootloader without wiping data. Even the OPO toolkit says you need to wipe data to unlock your bootloader.
One thing I haven't looked too much into is using fastboot to save my device. This guide http://www.technobuzz.net/fix-bricked-dead-oneplus-one-easily/ shows to flash userdata userdata_64g.img, which I assume wipes userdata.
Maybe I'm just overlooking some simple fix, but if anyone can help me I would be eternally grateful.
Edit: I need my phone working and I'm tired of waiting for help, so I just did a factory rest. Also I've been getting tons of conflicting advice. Thanks everyone for the help anyways
kinda on the same boat here.
may i ask how you set up adb? i cant get it to work
mastersen901 said:
kinda on the same boat here.
may i ask how you set up adb? i cant get it to work
Click to expand...
Click to collapse
download and install the 15 second adb/fastboot installer (http://forum.xda-developers.com/showthread.php?t=2588979)
It'll create a folder: C:/adb, In that folder you can open a cmd prompt window to send cmds to your device through adb/fastboot. that folder is also where you place files that you want to flash or boot into.
Also for the USB drivers just download the oneplus one toolkit, or use this guide: http://www.technobuzz.net/install-oneplus-one-usb-drivers-windows/
the opo toolkit is in the 2nd method
Still looking for help. Phone status: After sideloading cm 12.1 it boots up but I get tons of errors saying com.android.phone failed/ android.system.acore failed which make my phone inoperable, also my phone usually reboots after ~10 seconds after booting up and getting errors.
when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?
itechy said:
when you flashed the stock zip via sideloading did you use the full zip or the incremental zip?
Click to expand...
Click to collapse
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...be76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip
woodhaus said:
The zip I sideloaded was cm-12.1-YOG4PAS1N0-bacon-signed.zip (http://builds.cyngn.com/cyanogen-os...e76f9310/cm-12.1-YOG4PAS1N0-bacon-signed.zip)
I'm pretty sure it's the full zip
Click to expand...
Click to collapse
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs
itechy said:
You will have to flash the latest version as performing a downgrade without wiping data will cause issues like the ones you are seeing
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:
woodhaus said:
I can't really find a full cm13.1 zip. On CyanogenMod I only see up to 13.0. I also don't know how to tell the difference between an incremental and full zip D:
Click to expand...
Click to collapse
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs
itechy said:
Visit the support page I grabbed my full update zip from there https://cyngn.com/support
Sent from my A0001 using XDA Labs
Click to expand...
Click to collapse
Ohh! thanks! I was looking for this!
I just got around to sideloading the cm 13.1 zip. I'm still getting a bootloop /:
Edit: My phone reboots and optimizes apps after getting hung up on the cyanogen boot screen for a while.
I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.
hibernick said:
I'm in the same situation.
It seems like a cache cleaning is needed but I have no idea whether it possible without a custom recovery and without a full adb support.
Click to expand...
Click to collapse
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.
saurav007 said:
You can wipe cache partition in stock recovery also. To boot into recovery mode first power off your device. Press Volume down + Power button together until you see oneplus logo. When device is in recovery mode press volume down and select 'wipe cache partition' and press power button to confirm the action. Reboot after process completes.
Click to expand...
Click to collapse
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.
hibernick said:
The same like woodhaus I have locked bootloader and there is no USB debug over adb.
I don't have a 'wipe cache partition' in the recovery.
The only things I can use are adb sideload and fastboot.
Click to expand...
Click to collapse
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete
woodhaus said:
I have wipe cache partition but it doesn't seem to do anything. also it takes like 35 minutes to complete
Click to expand...
Click to collapse
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.
hibernick said:
How did you do it?
You told you are on stock recovery. Me either and I don't see such option in my recovery.
Click to expand...
Click to collapse
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition
woodhaus said:
it's under the factory reset option from the main menu on stock recovery
stock recovery>factory reset> erase cache partition
Click to expand...
Click to collapse
Oh, thanks. I didn't even go there.