Related
Hello friends,
So I wanted to switch my TF101 to Cyanogenmod this weekend. I've been using Revolver, but with other devices on CM, I wanted some consistency in the experience among my devices.
I started by updating my Clockworkmod Recovery version. Flashing the latest 6.0.1.3 version caused problems with Install Zip from Sdcard, for some reason. So I downgraded to the 5.8.3.4 Touch version. Now Recovery works, but I cannot utilize adb reboot-recovery (it reboots system), Reboot System Now from CWM (it reboots recovery), or manually power off to reboot system (it reboots recovery). I can manually reboot back to system by Power+Vol Down and letting it cold boot, but this is less than ideal.
Here's my big problem. I went ahead with trying to flash CM anyways. I booted into the recovery, with the CM zip on my sdcard partition. I wiped cache and data, flashed the sdcard, and then tricked my tablet into cold booting (sigh). Then I waited. CM's logo spun around, and around, and around...and did this for the better part of an hour.
So I tried flashing it again. Same problem. I would have tried flashing back to Revolver, but apparently the new CWM looks for my internal partition rather than my microSD card, and that's where Revolver is stored. Bad luck there.
I went hunting for some unbricking tools. I got the tablet into APX mode once, and got my computer to recognize that something was there. But by the time I'd installed the drivers, Windows wouldn't recognize that anything was connected. So I can't use any APX tools.
tl;dr: Here's my problem:
Bootlooping ROM
Recovery Access (CWM Touch 5.8.3.4)
No ADB access
No APX access
jordanjay29 said:
Hello friends,
So I wanted to switch my TF101 to Cyanogenmod this weekend. I've been using Revolver, but with other devices on CM, I wanted some consistency in the experience among my devices.
I started by updating my Clockworkmod Recovery version. Flashing the latest 6.0.1.3 version caused problems with Install Zip from Sdcard, for some reason. So I downgraded to the 5.8.3.4 Touch version. Now Recovery works, but I cannot utilize adb reboot-recovery (it reboots system), Reboot System Now from CWM (it reboots recovery), or manually power off to reboot system (it reboots recovery). I can manually reboot back to system by Power+Vol Down and letting it cold boot, but this is less than ideal.
Here's my big problem. I went ahead with trying to flash CM anyways. I booted into the recovery, with the CM zip on my sdcard partition. I wiped cache and data, flashed the sdcard, and then tricked my tablet into cold booting (sigh). Then I waited. CM's logo spun around, and around, and around...and did this for the better part of an hour.
So I tried flashing it again. Same problem. I would have tried flashing back to Revolver, but apparently the new CWM looks for my internal partition rather than my microSD card, and that's where Revolver is stored. Bad luck there.
I went hunting for some unbricking tools. I got the tablet into APX mode once, and got my computer to recognize that something was there. But by the time I'd installed the drivers, Windows wouldn't recognize that anything was connected. So I can't use any APX tools.
tl;dr: Here's my problem:
Bootlooping ROM
Recovery Access (CWM Touch 5.8.3.4)
No ADB access
No APX access
Click to expand...
Click to collapse
Reconnect tablet into APX mode, if u have installed all drivers laptop should recognize your tablet in APX mode... once in apex, use easy flash
Sent from my Transformer using xda app-developers app
You didn't read, clearly.
No worries, I got this unbricked by following this guide: http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Hey Your in the right place
Shoot me an email, we can review your issues and if we find a solution we can post back here to help
XDA users with there issues....
My email is everywhere talke a look around
Thx Josh
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Sounds like you are on an old bootloader. Flash the stock rom from asus by unzipping the zip you download from their website and placing in the root folder of your micro sd and then go into rck from the bootloader menu (power + volume down whilst booting)
Or you could just flash it from recovery....
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Asphodele said:
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Click to expand...
Click to collapse
I buy a tf700 with cm 11 a few days ago i am really interessted on how this steps works. I really want to make it unbrickeable, But i dont really understand how it works. I can not enter in fastboot. at least i got cwm interface when rebooting with adb into recovery.
Can u explain how you did it?
It invovles flashing a modified bootloader and the flatline recovery and then using Wheelie to generate your nvflash blobs.
Step-by-step instructions (which you need to follow to the letter) are here:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Stuck in boot loop, fastboot and recovery accessible
Hello,
I'm having a similar issue and I need help! Initially my tablet was rooted with Cromi-X 5.4. Then I decided to try Crombi-KK.
Here is what happened:
- Updated TWRP recovery
- Did a full wipe as recommended
- Flashing got stuck at the Crombi-KK loading sign
- Tried to reflash but TWRP wasn't detecting data partition anymore
- Instead installed the other recommended recovery CWMR.
- Flashed Crombi-KK, it worked. Played around with it for a few days, it was wonderful, fast and responsive.
- Battery died out and when I turned it back on I got a UIDs system inconsistent error.
- I found online many recommendations to reflash so I tried to do that
- Since then I'm stuck in a boot loop. I see the initial "bios" Asus logo then it restarts over and over.
- I am able to access bootloader and recovery
I've tried reflashing the asus stock blob. I've tried wiping the data through CWMR but it starts working and then it restarts. I don't know what to do anymore, so if anyone can help me, I would really appreciate it!
Thanks
Which recovery and bootloader version do you have now?
A (for KK) outdated bootloader seems the most likely culprit.
You can try save the recovery log when you flash or grab a logcat of the bootloop, but probably it'll only tell you that the recovery cannot mount /data.
Determine that you are on the correct bootloader, if not update it. If you're lucky the tablet will start right up. If it doesn't, formatting /data is the only way I know to get it back. Not just wiping - formatting it. You will loose everything on internal SD, so I hope you have a nandroid you can restore from later.
If you use TWRP 2.7+ be aware that formatting can take more than an hour. Let it finish!
For good measure, download CROMBi-KK again, check the md5 and then flash that file.
I'm on 10.6.1.14.10 bootloader which I think is the latest one
I have 6.0.4.7 CWMR
I'm trying to format data completely but when i do it in CWMR it starts and then the tablet reboots on it's own after a couple of minutes.
How can I retrieve the logs, I never had to do it before.
Thanks for your help
Mhh, getting a little more complicated.
Your BL is ok...
What do you see in CWM when you go into Mounts and Storage? What is mounted?
The recovery logs are under Advanced > show logs.
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
yasyas said:
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
Click to expand...
Click to collapse
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
sbdags said:
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
Click to expand...
Click to collapse
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
yasyas said:
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
Click to expand...
Click to collapse
To be in the safe side, yes, that is what I would do. TWTRP 2.7.+ takes a long time to format and it may seem the process got stuck. Give it at least 90 minutes to finish.
Then reflash CROMBi
I'm back up and running !!!
This time installing TWRP, everything was mounted (maybe my previous flash before CWMR wasn't good), did a format data, waited until it was done, flashed latest Crombi-KK and going through setup now. Hopefully won't have the same UID issue on next shutdown. I didn't enable fsync or journaling so hopefully it won't happen again.
Thanks both of you for your help!
Good deal! Happy for you!
Rooting google pixel zl
Phone: LG Spectrum
ROM: Cyanogen 10.1 3 or something
CWM: 6.0.4.7
I was in the process of manually installing CWM Touch via Rashr Flash Tool to replace an old 6.0.1.1 non-touch version i had on it before, and when I successfully got it installed, the app asked if I wanted to reboot into recovery. So I pressed yes, and it did.
Unfortunately, it never seemed to remove it afterwards because after every single reboot, it kept going back to recovery, not loading the android OS.
I've tried the following with no success:
Clearing data factory reset
Clearing cache
Clearing Dalvik cache
Full restore to V6 stock
Full restore to Cyanogen (I made a backup when I first got to CWM Touch)
This is the current behavior of my phone:
When powered on, it will display the LG logo, then it will flicker to black and then fade in the LG logo again, 5 seconds later recovery boots. If phone was off and you insert USB cable to charge, the LG logo appears, but the battery mode sort of screen never comes after. Its just stays at the LG logo, and never turns off the display.
It will keep rebooting to recovery no matter if I even tell the recovery to reboot to bootloader.
I don't know exactly how the bootup structure is for androids but the only thing I can think of that may be the issue is the recovery itself if it wasn't the app that caused this. It just doesn't make sense that after a full restore, it would still have an issue, other than the recovery itself, UNLESS there is some secret boot instruction file that's stuck with a "Reboot_to_Recovery = 1" parameter.
Since this thing is stuck in a recovery boot, how would I be able to manually, without OS access, reflash another version of CWM on the device? Or if there's another possible way to fix this, please help me.
Maybe the ROM hasn't flashed on your phone properly .try again with a clean flash. may help
HiT Thank$ If HelPed
I believe this is independent of the ROM. I had noticed in preparing to flash a new ROM that instead of restarting to the OS, it restarted to the recovery. I didn't take much note of this, but it was clear that this problem began when I flashed the new recovery. Also, the fact that I had used 2 seperate, very different restores (full restores) with no success means that it couldn't have been the ROM.
My only probably clue right now is that the recovery is to blame (which is weird since CWM notes 6.0.4.7 as compatible with LG Spectrum. I had 6.0.1.1 before with no issue). I have no idea how to change this recovery however, given that I can't even boot the OS at all, and there doesn't seem to be a "flash recovery' option in recovery (which is kinda annoying).
Hey guys. I'm a bit of a newbie at androids. I bought a Moto G, and I decided to root it.
I realized that the android was not unlocked, so I went through a small progress to try get it unlocked so I could install a custom recovery. I chose CWM.
I went through a tutorial on how to install CWM, and I installed it. I used the MotoTool to push Superuser to my android, and was able to install the zip.
It all went wrong when I tried to exit out of CWM.
I selected "Reboot" and it loaded the screen up to CWM again...a bit odd. So I'm trying to reboot so I can use my phone properly, and nothing is working.
What I've tried :
-----> Clearing dalvik cache and cache with CWM -
I tried this and it still didn't work.
-----> Loading into my AP Fastboot with CWM and trying to power off and on from there
Still didn't work and loaded into CWM.
----->Flashing my bootloader
Made it worse. I can't even power up my phone anymore.
In conclusion, my phone is hard-bricked, and I can't even power it up. If anyone has any solutions, it would be extremely helpful. Please feel free to comment or reply if you need more info about my device.
everything was working fine for almost a year. twrp, magisk, everything was working as intended. decided to update to the july stable build (walleye-pq3a.190705.001) and decided id like a fresh start. ok cool, easy enough, just boot into the bootloader/fastboot mode and use the flash-all script, done. flash TWRP 3.3.0 using "TOOL ALL IN ONE". installs fine, reboots fine, cool. reboot to recovery to install the magisk 19.3 zip. wait what? password not accepted? it works in system, and is the same password i always use for the phone (i just use one to prevent butt dialing). ok fine whatever lets just reboot and completely remove all security for now, and figure that one out later. reboot into twrp, no password this time. excellent. lets flash this zip (same zip that i downloaded directly from magisk manager before starting any of this, also tried an old copy that i used to root the first time). everything looked like it was fine, so i rebooted to system. waited about 3 - 5 minutes, and it rebooted to recovery. hmm, odd, maybe just a bad cache or something. rebooted again. same thing, kicked back to recovery. ok, lets do dalvik/cache. nope, same problem. redid flash-all, and manually installed TWRP using fastboot to boot an img, push the twrp installer zip, flash that. same problems. changed slots, flash-, manual twrp flash, same problem. factory reset, repeat flashing, same problem. format system and data partition to get rid of everything, reflash, same problem. theres other stuff that ive tried that i dont remember too.
EDIT: also tried restoring an old TWRP backup from feb. and got the yellow auth error on the bootloader
where i currently sit is i can get a factory image on there and can get twrp on there, and even flashed lineage just for ****s and giggles, and that even worked (esim manager kept crashing, didnt test much else, but it booted and was functional for what little i tested).
TLDR: twrp wont accept pin, and when i disable the pin and flash magisk i can no longer boot even though these are the same files that have been on my E drive since the day i got it, which worked fine back then. it almost feels like theres some kind of corruption somewhere.