Related
hi guys, i'm noob for a android, i switched from iphone to HOX at&t, and i really like it. Last night I tried to root, unlock bootloader, and flash custom ROM to my phone. The root part was easy, and unlock bootloader kinda tricky but I did it. After unlocked bootloader I tired to install twrp recovery to it, but i think my phone lost root, because I tried to use titanium to backup my apps but it said my phone doesn't have root, even though i saw the SU icon. I gave up since I was tired. This morning I still could turn on my phone and work normally, then I went to bootloader mode and I saw the recovery, I wiped cache, cavilk, system, and factory reset, but when I tired to reboot system, it wouldn't work, so I had to volume down and power button to get back to bootloader mode. I tried reboot in there but my phone stuck in HTC logo and I can't do nothing. I don't know what to do now. I tried to reboot on cmd but it still stuck at HTC logo. I tried to install the custom ROM by cmd but it was erro: device can not found. I think my laptop doesn't recognize my phone even though I already installed HTC driver. I thought when I plugged my phone in bootloader, choose fastboot, i saw fastboot usb though, so my phone connected.
natetruong said:
hi guys, i'm noob for a android, i switched from iphone to HOX at&t, and i really like it. Last night I tried to root, unlock bootloader, and flash custom ROM to my phone. The root part was easy, and unlock bootloader kinda tricky but I did it. After unlocked bootloader I tired to install twrp recovery to it, but i think my phone lost root, because I tried to use titanium to backup my apps but it said my phone doesn't have root, even though i saw the SU icon. I gave up since I was tired. This morning I still could turn on my phone and work normally, then I went to bootloader mode and I saw the recovery, I wiped cache, cavilk, system, and factory reset, but when I tired to reboot system, it wouldn't work, so I had to volume down and power button to get back to bootloader mode. I tried reboot in there but my phone stuck in HTC logo and I can't do nothing. I don't know what to do now. I tried to reboot on cmd but it still stuck at HTC logo. I tried to install the custom ROM by cmd but it was erro: device can not found. I think my laptop doesn't recognize my phone even though I already installed HTC driver. I thought when I plugged my phone in bootloader, choose fastboot, i saw fastboot usb though, so my phone connected.
Click to expand...
Click to collapse
boot into bootloader and choose fastboot. connect to computer and fastboot oem relock bootloader, then run the RUU. if all goes well you can then reunlock the bootloader with the unlock_code.bin you used to unlock it the first time.
Don't RUU back all you did was wipe the phone completely no big deal. Just load into bootloader select recovery then mount the usb storage upload a custom ROM CleanROM, AOKP or CM9 your choice really and then unmount usb storage then flash the custom ROM all fixed.
PS the reason your got stuck is when you wipe /system that wipes the ROM completely.
P_Dub_S said:
Don't RUU back all you did was wipe the phone completely no big deal. Just load into bootloader select recovery then mount the usb storage upload a custom ROM CleanROM, AOKP or CM9 your choice really and then unmount usb storage then flash the custom ROM all fixed.
PS the reason your got stuck is when you wipe /system that wipes the ROM completely.
Click to expand...
Click to collapse
+1 to this. You will be fine if you just flash another ROM.
And for future reference (if it wasn't obvious already), don't wipe /system
P_Dub_S said:
Don't RUU back all you did was wipe the phone completely no big deal. Just load into bootloader select recovery then mount the usb storage upload a custom ROM CleanROM, AOKP or CM9 your choice really and then unmount usb storage then flash the custom ROM all fixed.
PS the reason your got stuck is when you wipe /system that wipes the ROM completely.
Click to expand...
Click to collapse
Thanks man, I did and it works!!! Thanks million times hehe Enjoying the custom ROM
Hi all,
So, last night I successfully rooted and unlocked my One X on AT&T. Today, I tried putting a ROM on it. I flashed the boot.img first, then tried to install the ROM (Jelly Bean Sense). It failed for some reason, so I wiped and rebooted my phone.
Instead of going back to the stock ROM, the phone now will not turn on, is not recognized on both laptops I tried, and does not recognize even being charged. The only thing that happens is when I press down the power button, all of the soft keys illuminate and flash until I stop holding it. I've managed to get into the bootloader screen once, but the phone reset itself before I could do anything.
The only screen I can get to with the Vol Down+Power combo is the HTC Screen, but it's the one that shows before my custom recovery, with some warning from HTC in red letters at the bottom.
At this point, I just want a phone that works. This is a lot more complex [for me] than rooting and flashing a ROM to the Inspire I had for some reason. I fly out for vacation in two days for a few weeks, so I'd like to be able to avoid having to send this thing back to HTC or AT&T if possible.
ANY help is greatly appreciated.
If it's easier, feel free to Skype chat me.
Thanks!
Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Im confused.. it won't come on, but you can get to recovery? If you can manually boot into twrp you'll be fine.. may I ask which Rom you flashed? Did you flash the boot.img first? Or after you flashed Rom? Alot of guys will say flash boot.img first.. I don't have that funky hboot but I have to do my cousins alot and his will only boot correctly if I flash Rom first, then boot into bootloader and fastboot the boot.img.
Try that and let me know how it goes
Also... Let go of all the buttons when you see the white screen lol. That means you found bootloader
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I can get it to boot into the Bootloader screen and the TWRP now just fine, but that's as far as it will go. The internal SD will not mount with TWRP either now.
Here's the ROM I tried to flash: http://forum.xda-developers.com/showthread.php?t=2055490
I put it on my SD card, then extracted the boot.img to the folder I have my dab/fastboot files in, then flashed the boot.img, then tried to flash the ROM.
If I can get it working again, I'll try to do it in reverse order next time and see if that works. Still trying to find a way to get a ROM on here with my Mac, and to make my SD card work again. Everything on it is backed up so it's ok if I need to wipe it.
If you can get to bootloader, you're not bricked. It's just a matter of flashing the right stuff in the right order.
It could be that your sdcard is corrupted. Factory reset from bootloader will do it, but fixing it just a matter of formatting it again. Can you mount it on your computer? What happens when you plug into your PC?
Your sdcard is corrupt. No big deal but you'll lose everything. Plug it in into computer and locate the storage and try to find a way to format it. Sorry, I have no clue with a mac I swore off apple products :thumbup:
Anyway, you seem to know the ropes for the most part. If you can format, drag Rom onto SD. Wipe everything in twrp. Cache, dalvick, factory reset, system. Flash Rom.. immediately boot into bootloader and fastboot the boot.img. choose reboot from bootloader. Good luck!
Sent from my HTC One XL using Tapatalk 2
Yep, I also suggest doing a factory reset from the bootloader ( which will erase your internal storage) but at least you'll be able to mount your SD card, put a ROM on it and flash it. I would highly recommended you to flash viper 3.0.0, you don't need to flash the boot.img and its pretty much stock JB with some tweaks.
Sent from my HTC One XL using Tapatalk 2
I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?
That's good news!
I tried doing a factory reset from bootloader, but nothing happened. Maybe because the SD card won't mount?
I only have a Mac, with no PC in sight. It doesn't show up at all on here. Fastboot USB, or when I mount it as USB in TWRP. It does however show up as a device in recovery in terminal. But nothing on the desktop. Apple+Android do not mix well!
I'm ok with losing my data, what I'm not OK with is having to use this pink Razr while my nice phone is broken :'(
Thanks for all the help so far!
I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.
elijahpr said:
I do a factory reset from bootloader, it takes me into TWRP. Now is the only time it will even remotely show up on my laptop, and even then it's only via terminal when I do adb devices. Since it can't mount for some reason, is there a way to reformat via Terminal, and maybe even push the ROM to my phone from there? That's something I'm not familiar with.
Click to expand...
Click to collapse
Format your sd..drag Rom..wipe..flash..enjoy
omario8484 said:
Format your sd..drag Rom..wipe..flash..enjoy
Click to expand...
Click to collapse
I can't format because it doesn't show up on my computer, and doing so in bootloader takes me to TWRP.
emylibef said:
I am having this same problem (minus the custom screen).
My phone will boot into TWRP and all, but it won't mount (PC says the disk needs to be formatted before it can be used). When I go to reboot or anything from TWRP, it tells me there is no OS installed and am I sure.
Can anyone help?
Click to expand...
Click to collapse
Hey dude, I followed their advice (dug out my XP machine) and now my SD card is re-formatted.
Get into the bootloader screen, hit factory reset. (When I did this on mine, it took me right to TWRP)
From there, I mounted as USB and it showed up as needing to be reformatted on my XP machine. Took a few minutes to do on this dinosaur, but it worked, cause everything is gone!
Right now I'm in the process of zipping up the Viper XL ROM (thanks for the recommendation barondebxl, it looks awesome!), which I'll put onto my SD card and wipe/flash from there. (on my Mac now).
Hopefully it works!
I'm unable to flash ROMs for some reason. It doesn't give an error, just says that it failed. Any ideas?
elijahpr said:
Get into the bootloader screen, hit factory reset.
Click to expand...
Click to collapse
No no no. This is what is corrupting your sdcard. Only do a factory reset in TWRP or once booted up. Start over and format again. Then copy over your rom.
When you and a few others mentioned doing it, what were you referring to?
I've tried three different ROMs now, and each fails without saying why in TWRP.
Problem solved! Got the stock RUU back on there and it works perfectly. Just re-rooted and unlocked again. Round two..
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).
Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?
fastboot reboot-bootloader ; just after recovery flash.
Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Click to expand...
Click to collapse
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
twrp not boot after successfully flash in this rom
Sanarise said:
Unfortunately, I can't.
Trying to boot into TWRP just gets stuck on the 'Redmi' boot logo.
I just remembered that you can install TWRP over ADB, and that Peter's one says it works even when the system partition is empty, so maybe the issue is the TWRP I installed and could possibly undo this part of the issue over ADB.
It won't fix the issue preventing my from updating my rom, but recovery only is still better than a soft brick.
Edit: That worked, i've put Peter's TWRP back on, and it's launching into recovery mode/TWRP again now
Click to expand...
Click to collapse
flash latest twrp download from github, install twrpbuilder img twrp ,it boot fine and you will copy your data to pc and then install any other twrp img which u want , dont wipe anything from phone before phone boot.flash only original twrp builder 3.2.3.1 official,it boot only on latest updates.
Why nobody use orangefox?
is your issue solve or not tell,
Simoom Sadik said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
first click on extract a fastboot rom and copy boot system and vender file with flash.all bat file and make a new folder then click on flash.bat save user data file to flash these images
or you can do this manually
fastboot flash system system.img
fastboot flash vender vender.img
fastboot flash boot boot.img
then reboot device to fastboot again
now flash latest official twrp builder 3.2.3.1 img twrp and take all your data backup,
in fastboot flash latest miui do not downgrade direct otherwise you lost your data,
after this if you sucess then you can flash your old rom which is running before issue of boot loop of redmi logo
it will deincrypt your data safely and then root device and boot normally, if you lost anything then contact me with mail or whatsapp i will help you,7009197673 india
and this twrp work on all version from chines to global beta stable and indian stable
joke19 said:
Why nobody use orangefox?
Click to expand...
Click to collapse
In the end, I did try orangefox, and it might have been part of why it worked.
However, the crDroid installation instructions specifically mentions using Peter's TWRP, so I initially used that one.
anmoltinder said:
if your problem is not solve then tell me you need to flash a fastboot rom first with save user data.bat file and when it installed then you can install twrp builder 3.2.1. and then boot to twrp this methods working fine,if you recently flashed any android 10 rom then first you need to flash a miui fastboot rom,or flash it via command mode direct only 3 files
Click to expand...
Click to collapse
Thank you for the effort you put into typing up a guide to help me, but I ended up fixing my own problem.
I was able to use fastboot to flash on a better TWRP release, and then get the rom to install properly by installing fcrypt-disabler just after it.
Sanarise said:
Today I tried to finally update to the latest version of crDroid, but ended up having a bunch of issues doing so, and after a lot of troubleshooting and trying to fix it, I ended up putting it into a bootloop of some sort instead.
I'm pretty sure the last thing I tried was installing a different version of TWRP to see if that version would let me properly install the rom, and stop my phone from always rebooting into recovery mode.
Trying to turn it on normally or boot into TWRP leaves it hanging on the "Redmi" boot screen, it can boot into fastboot mode though.
I'm guessing that the only way to recover my phone at this point is to flash the Official MIUI rom back onto the phone, but that also involves wiping Data and losing pretty much everything I've put on the phone.
I was smart enough to make a TWRP of the Data folder, but while making the backup, the console said it doesn't include all personal files or something.
How much of my personal data and files can I rescue from the phone in this state, and how can I do that before it gets wiped when fixing it?
Also, I think I really need some help in actually restoring my phone and flashing the custom rom properly.
No matter how much effort I put into figuring out how to do this stuff, unexpected issues always seem to happen, and turns something that initially seemed so simple into multiple hours of troubleshooting.
The only way I think i've gotten rom flashing to work at all was by wiping everything and installing the official MIUI rom, but I don't want to be losing my data every month when an update comes out.
So, could someone please help me get my phone working again?
Edit: I ended up fixing my own issue by ADB flashing on a different release of TWRP, and then installing fcrypt disabler after the rom but before everything else.
Click to expand...
Click to collapse
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Fcsubxrhi said:
help.I woke up yesterday and I turned on my phone and it is stuck on the Mi logo.All i can do is get it to fastboot thing.It seems like you and I have the same problem and I would love to have some help from you
Click to expand...
Click to collapse
If you can access fastboot, then flash TWRP.... Enter recovery, wipe your system partitions and then flash the Stock MIUI ROM or use the MiFlash tool. Make sure you aren't flashing an older version of the ROM than the onle already installed.
CongestedHangman said:
can u boot into twrp?
if u can boot, while in twrp, connect your phone via usb cable to pc. u can copy everything on pc
Click to expand...
Click to collapse
I have the same problem that stated after installing the update for derpfest and I can boot into twrp. Any solution for me?