Hi guys
I hope you can help. Ive been triying all day yesterday to root another rom to replace my cleanrom 4.1.1.
I run CWM 6.0.2.1 tried to flash several different roms withuot succes. Tried to flash CM10.2 but it hangs duing the boot screen. Tried to flash A newer version of clean rom but it hangs on the startup screen.
I did read on the internet that you need a newer recovery to flash a newer rom. So i tried to flash anther recovery. The problem is that fastboot does not see my tablet. My windows 8.1 PC recognizes the tablet but fastboot says waiting for device
I even tried to flash my tabet on a XP VM, but it wont recognize my tablet at all,
The funny thing is that i can flash my old cleanRom version 4.1.1 without any problems
iaudio87 said:
Hi guys
I hope you can help. Ive been triying all day yesterday to root another rom to replace my cleanrom 4.1.1.
I run CWM 6.0.2.1 tried to flash several different roms withuot succes. Tried to flash CM10.2 but it hangs duing the boot screen. Tried to flash A newer version of clean rom but it hangs on the startup screen.
I did read on the internet that you need a newer recovery to flash a newer rom. So i tried to flash anther recovery. The problem is that fastboot does not see my tablet. My windows 8.1 PC recognizes the tablet but fastboot says waiting for device
I even tried to flash my tabet on a XP VM, but it wont recognize my tablet at all,
The funny thing is that i can flash my old cleanRom version 4.1.1 without any problems
Click to expand...
Click to collapse
What bootloader are you on, you may have to upgrade the bootloader before flashing any current roms. Also try using running fastboot in Windows 8 test mode.
cmendonc2 said:
What bootloader are you on, you may have to upgrade the bootloader before flashing any current roms. Also try using running fastboot in Windows 8 test mode.
Click to expand...
Click to collapse
I cannot find anything about flashing the bootloader, if you mean a recovery, i already tried. In the past i had to flash a boot image using fastboot, but since my pc does not recognize the device in fastboot mode, i cant do anything
iaudio87 said:
I cannot find anything about flashing the bootloader, if you mean a recovery, i already tried. In the past i had to flash a boot image using fastboot, but since my pc does not recognize the device in fastboot mode, i cant do anything
Click to expand...
Click to collapse
upgrading the bootloader involves flashing the stock ROM. That can be done via the TWRP installed on your device, which you said can flash ROMs like CleanRom
cmendonc2 said:
upgrading the bootloader involves flashing the stock ROM. That can be done via the TWRP installed on your device, which you said can flash ROMs like CleanRom
Click to expand...
Click to collapse
This also involves fastboot, witch doesnt recognize my tablet (the pc does, but fastboot does not)
iaudio87 said:
This also involves fastboot, witch doesnt recognize my tablet (the pc does, but fastboot does not)
Click to expand...
Click to collapse
You'll need to get that working then. It's not hard just need to install the drivers from XDA - try the naked universal drivers first.
Related
Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?
I had that once when I installed stock. I fixed it by going into recovery and clearing cache and dalvik
Sent from my Nexus S using XDA App
I can't boot into recovery though - It's missing.
theadb said:
Totally n00bed my Nexus S.
Was running the latest Miui and installed ROM Manager. Decided to download stock Android and install.
Now the phone is boot-looped (stuck on the Nexus boot image) and Recovery seems to be gone.
I tried pushing the recovery image file but adb won't detect the device.
Any advice?
Click to expand...
Click to collapse
you need to install the proper nexus s drivers.easiest way is to go to the pdanet website http://junefabrics.com/android/ , download their free product, and let it install the drivers for you. did you flash the recovery through rom manager originally? anyways, then wipe(data. factory reset) and reflash the stock rom. you always have to wipe before flashing a DIFFERENT rom, or youll get stuck in a bootloop.
I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)
theadb said:
I installed the 64-bit drivers from PDA already but I'm running XP 64-bit (could that be the issue?)
Click to expand...
Click to collapse
maybe?????
Will adb still work even though I can't boot my phone and turn usb debugging on?
Unfortunately I have 64-bit windows at work, but I'll try on my Win7 or Mac at home.
Still can't get adb to or fastboot to recognize the device...maybe I'm missing something...
I have no recovery and can't boot - what can I do?
Bump. In the exact same mess.
I was on MIUI ICS and tried to go to a stock GB rom, ended up stuck at the boot animation in the fresh rom (which kept looping). Recovery was a no-go too. I tried using adb to push another stock rom which again, installed but got stuck at the boot animation. After that even adb stopped detecting the phone.
What do I do now? theadb how did you fix it?
ADB is working as I plugged in my HD2, which was detected immediately.
Er bump?
Use fastboot to flash a new recovery, then boot into recovery and do what is needed. Recovery will probably be replaced by stock each time you attempt to boot into android while the stock ROM is installed.
I'm in the exact same situation and I don't really think there's anything we can do. We can't enter fastboot. We can't go into download mode. We can't boot into recovery there is literally zilch that we can do to fix the phone.
After trying to install CM10 Via TWRP my phone hung on the CM10 splash page.
I have tried to reinstall CM10 and I keep having the same problem.
I'm able to access TWRP but for some odd reason I can't mount my sd card properly. I'm not able to click "Mount sd card" on the "mount" page in TWRP. That being said I can't backup my phone from a previous backup.. Any help would be greatly appreciated.
Now my phone won't even turn on.. HELP
undergrad said:
Now my phone won't even turn on.. HELP
Click to expand...
Click to collapse
Have you tried holding down the power and volume down button for longer then 10 seconds or longer? this should force restart your phone, get into TWRP and try an other Rom for now, also did you try an international rom? international roms will not work.
UPDATE: I'm guessing your also can't recover your last back up because your on HBOOT 1.14 S-ON? 1.14 will not recover boot.img's
If you manage to get it to mount to your computer (Check your drivers are installed also, EG htc sync usb drivers) then look for a "one click boot img flash" unless you know how to flash them using fastboot commands, whenever you are to flash a room, extract the boot.img from the zip file, flash that in fastboot, THEN go to recovery and flash a rom. same goes for backups. S-off is a hassle.
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
undergrad said:
My computer recognizes that the phone is being plugged into the computer but it can't install the proper drivers.
Sadly I can't get my phone to go into recovery either.
Click to expand...
Click to collapse
when in twrp recovery.
1. delete cache, dav. cache, and system restore.
2. reinstall the gapp files and the CM10 zip file.
3. reboot
The issue is that I can't get into TWRP
what did you do to it? phones don't just die and cm10 didn't kill it. are you sure you flashed cm10 for the evita?
also try flashing this version of twrp openrecovery-twrp-2.3.3.1-evita.img
also run "fastboot erase cache" after flashing then try going into recovery and wiping cache,dalvik, and external
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
undergrad said:
I'm trying to fix it by using the HTC Android Phone ROM Update utility, but I keep getting the follow error.. "ERROR [140]: BOOTLOADER VERSION ERROR...
I'm not currently able to boot into TWRP to install a new ROM.
Click to expand...
Click to collapse
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Lemagex said:
well if you've unlocked your bootloader you cant upgrade with anything to do with htc and that's sure to mess with it. you're on your own sources of updates, no OTA nothing. You need to install htc sync and adb drivers for your phone if that still doesnt detect then its a usb brick and I'm of no hope but others may be
Click to expand...
Click to collapse
I managed to relock my bootloader, but installing the stock RUU is still another story..
I can only get my computer to recognize that the phone is connected to my computer if I'm in Fastboot mode.
If you can't mount from recovery the sd got corrupted happened to me they have a fix if you do a few searchs. If you locked the bootoader and the computer only recognizes in fastboot that is good now run a RUU like 1.85
Sent from my HTC One X using xda premium
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
ttakacs said:
After months of flashing everything in sight on my NS4g, the device appears to have rolled over and died! It started a few days ago, when it rebooted and asked me for a password to decrypt from storage (no password has ever been set). I couldn't get past that screen, so I decided to boot into recovery (TWRP), reinstall ROM (CM10) and gapps and restore data from backup.
No go. It just kept rebooting into recovery. But I was able to connect the phone to the PC and copy files from the phone but could not copy or delete files on the phone from the PC.
I used fastboot, Odin, and one-click-stock to wipe the device and install factory images, but the phone would boot no further than the red triangle-dead android.
Is my phone dead? I searched the forums and couldn't find any solutions other than to do what I have already done.
Click to expand...
Click to collapse
When you flashed to stock you erased your recovery.. Reconnect to your computer and push a recovery onto your phone and you're good to go..
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
ttakacs said:
Unfortunately, when I flashed TWRP and boot.img to the phone using fastboot and attempted to boot into recovery, bootloader reports "No Boot or Recovery Img."
Click to expand...
Click to collapse
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Setting.Out said:
Try the Nexus tool kit and from the bootloader (power and vol. up) select flash to stock (bricked) then in advanced boot temporary recovery to flash the recovery of your choice.. or push a boot image.
Click to expand...
Click to collapse
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
ttakacs said:
Wish I had better news but ... using the Nexus tool kit I was able to boot into TWRP but when trying to flash CM10 and gapps for this phone the flash failed; likewise, I could not flash CM10 and gapps by pushing the files from the PC to the phone. I first did flash to stock (bricked) but that brought me back to the red triangle, dead android.
I am beginning to suspect that the phone internal sdcard is corrupted ... is there a way to test for that?
Click to expand...
Click to collapse
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Setting.Out said:
When you got it to flash to stock did it boot up fully?
Remember that flashing to stock removes custom recoveries and you will need to flash one
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
ttakacs said:
No, the phone never did boot up fully. It got to the Google screen with the unlock icon and then to the red triangle, dead Android.
Click to expand...
Click to collapse
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Setting.Out said:
This happened when you tried stock or custom?..
Did it fully boot on stock image?..
The dead android usually shows up when you attempt to boot into recovery and you don't have one... If you try to boot and you loop back to the dead android it usually means you don't have a rom...
Try again to flash to stock, use the toolkit to boot a temporary recovery and flash a custom recovery.. Then make sure you are flashing the correct rom and correct gapps for that rom and for your phone.
Click to expand...
Click to collapse
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
ttakacs said:
I know have a recovery because the tool kit booted into TWRP; furthermore, the tool kit installed a TWRP 2.3 image (prior to installing the tool kit I was on 2.5 so the tool kit did something). From there, I tried to flash CM10 and gapps in the sdcard/download folder, but that failed, with TWRP returning message similar to "error opening ZIP".
I have used Odin to flash the stock image and it did not fully boot, ending at the dead android. Same results for flashing the stock image using fastboot with the phone connected to the PC. Same results with using the Nexus tool kit to flash a stock image (first JB and then, when that didn't boot, ICS). And, after the toolkit booted into temporary recovery (TWRP), I tried to flash (in this order) CM10 plus gapps, JB stock, and ICS, each time with the same results (no full boot, dead android).
I am with you when you say that the dead android means there is no rom, because my efforts to flash any rom, whether stock or custom, don't do anything. To all appearance, the phone contains a bootloader and a recovery and nothing else.
Thanks for your persistence ... any ideas for something else to try?
Click to expand...
Click to collapse
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Sent from my Nexus S using xda premium
Setting.Out said:
I'm at a loss.. Try again, maybe there's something missing.. And flash only one at a time and see if it worked (just ROM then reboot) then wipe d+c and flash gapps reboot then wipe flash... Ect... Ect...
Click to expand...
Click to collapse
I am too. Every method known to me (Odin, fastboot, adb) to flash a ROM, whether custom or stock, has failed to boot. Thanks for hanging with me on this; if you can think of solution I'll be glad to have it. Or if I solve it, I'll post here.
So I flashed a new recovery, TWRP 2.6.0. When I try flashing a new ROM now, I'm getting the following error "Could not create file for updater extract in /tmp/updater." And for some reason, the ROM I had installed previously, TrickDroid 10, is no longer there, so there is no longer a bootable OS on my phone. I tried reinstalling the recovery I had before, TWRP 2.3.3, but I can't get my phone to connect to adb or fastboot. I installed the drivers, but neither command is recognizing my phone, even when in the bootloader.
I would really appreciate some help as I am completely stuck right now. No OS, not able to flash any ROM.
EDIT: I am not using S-OFF, and my hboot is 1.09.0000. I understand I have an outdated hboot, and newer ROMS such as the latest CM nightlies won't flash, but not even older roms, like CM 10.0 are flashing.
Also, to clarify my fastboot issues, Whenever I am in fastboot mode in recovery, it will only change to "FASTBOOT USB" if I scroll up or down - this happens regardless of if it is plugged in to the USB port or not. This used to work on my old comp, so I don't know why it isn't right now.
i think im having the same problem, can you access your sd card through your pc ?
If the "Fastboot USB" come red and you do not have plug in, then the bootloader could be mess up or you charge port "stuck". Does you phone charge, when plug in?. I would try to run RUU and see what happen.
Best bet would probably be to factory reset the whole phone. I had this happen once and I used a recovery I found on here, that puts it back to the stock recovery and let's you reset. From there you can do everything again
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
benjmiester said:
Hey guys.
I just got a very nice condition used TF700T. I am trying to get recovery to install so I can flash a rom. I used the Transformer Toolkit to unlock it, which worked, it says device unlocked when booting.
But I absolutely cannot get it to Root, or flash recovery. If I try using debugfs root generic 2.3 it fails to write everything. If I try to flash any recovery with the toolkit it downloads and says flashing but just sits at about 25%, it boots my device into the screen that says usb fastboot mode with the three icons that say RCK Android and factory wipe. If I click the RCK it says rebooting and then goes to android mascot installing icon, but then the one with an X and error appears. What on earth am I doing wrong?
Is it the latest 4.2 update locking me out? Can I downgrade? I just can't get anything to root or flash recovery no matter what I do. I feel a little defeated being a long time member and 3 phone habitual rom flasher :crying:\
Any ideas what i'm missing?
Click to expand...
Click to collapse
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
LetMeKnow said:
What custom recovery are you installing? You may want to try with fastboot or adb method to flash your custom recovery which doesn't require rooted device, good luck....
Click to expand...
Click to collapse
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
benjmiester said:
Well I tried TWRP 2.7.1.1 I believe and also CWM , and Phil's custom touch CWM that all three are options to flash with the all in one ADB Toolkit app via USB from windows (http://forum.xda-developers.com/showthread.php?t=2094746)
How do I do the Fastboot method? I read about that, but have no idea how the process goes. I'm ok with skipping root and going straight to recovery and a rom because I can just flash superuser after if the rom isn't rooted already.
Click to expand...
Click to collapse
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Unlocked bootloader is allowed you to install the custom recovery so you can install the custom ROM, I believed..... You can check this guide out to see if you can setup your fastboot/adb. It is very easy to follow for the beginners, good luck....:fingers-crossed:
http://forum.xda-developers.com/showthread.php?t=2688891
benjmiester said:
I wanted to try an app I used to get twrp onto my LG G2 for the first time called "flashify" that worked like a charm. I just installed the app, downloaded the twrp file and flashed it then it reboots to recovery, but it requires root as far as I know. Does unlocking the boot loader allow things like this?
Click to expand...
Click to collapse
Once you unlocked the bootloader you can flash a custom recovery and after that - the sky's the limit.
Flashify works great, and it is a wonderful tool as long as you're able to boot into Android.
My problem with Flashify and Goomanager and TwrpManger is that it saves users from setting up a proper ADB/fastboot connection from PC to tablet.
As long as you can boot Android, these apps are great. But what if you can't? Once the tablet doesn't boot it's so much harder (and often too late) to get the correct drivers installed for ADB and fastboot.
So if you flash your recovery with any of those apps still make sure you have access with ADB and fastboot from your PC.
You will regret it if you don't - I (almost) guarantee it.
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
benjmiester said:
That's an excellent point. Thanks. I did actually get the Fastboot method to work. The problem was that I kept clicking into RCK recovery when I ws supposed to just leave it on that screen to push twrp instead. I got recover and just got done doing a backup. I'm about the flash my first rom (http://forum.xda-developers.com/showthread.php?t=2672751). Do we need to do factory reset / wipe data/system etc? The instructions on the ROM post say to just flash it from twrp so I'm guessing it has a built in wipe feature during install?
Click to expand...
Click to collapse
The instructions in the OP actually say that you have to do a full wipe (Factory Wipe) in TWRP coming from a different rom base. Which would be you unless you had a version of CROMBi-KK installed prior to this.
It's the default selection under the Wipe menu in TWRP. Just do that and then flash the rom and your ok.
Do not use the Factory Reset option from Settings or the Wipe Data option from the BL menu! Do this in TWRP only!
Cool thanks. I figured so because that's the norm with roms on all my phones. Thanks a lot for the help guys. So happy to be get KK running on my new toy!
Just wanted to update. KK 4.4.3 rom flashed and booted in. It's much nicer. The stock was a little laggy, and KK breathed a lot of new life into my ancient single core 1.0 ghz Galaxy S that I use as a music player so I figured it would help make the tab real nice and snappy too. Gotta go now, much fun to be had!!