Well, a few things went wrong when I tried to install CM10 today. First, I rooted using Debugfs simple root. I then unlocked using the file on the Asus site. I then installed CWM through Rom Manager, and then wiped and installed CM10. I thought I had done a recovery, but it is no where to be found. So, now I'm stuck and can either go into CWM or I will get a black screen and it will sit there. I tried wiping and reinstalling same rom, but that is about all I can do. I haven't used ADB before so I just installed it and checked if it would see my device. It appears to see it when it gets to the black screen, but not when I'm in CWM. I'm a newb when it comes to this stuff, but never had problems getting CM10 on my atrix so i thought I would give it a shot. Anyone got any suggestions? I searched for about an hour for a solution and tried the IRC chat, but no luck. Do I have an expensive paper weight now?
larzred said:
Well, a few things went wrong when I tried to install CM10 today. First, I rooted using Debugfs simple root. I then unlocked using the file on the Asus site. I then installed CWM through Rom Manager, and then wiped and installed CM10. I thought I had done a recovery, but it is no where to be found. So, now I'm stuck and can either go into CWM or I will get a black screen and it will sit there. I tried wiping and reinstalling same rom, but that is about all I can do. I haven't used ADB before so I just installed it and checked if it would see my device. It appears to see it when it gets to the black screen, but not when I'm in CWM. I'm a newb when it comes to this stuff, but never had problems getting CM10 on my atrix so i thought I would give it a shot. Anyone got any suggestions? I searched for about an hour for a solution and tried the IRC chat, but no luck. Do I have an expensive paper weight now?
Click to expand...
Click to collapse
Yes you have a paper weight I'll give you $10 for it..... just kidding.... btw it aint bricked if you can get to cwm but thats another story..I will assume you have a windows 7 pc, for now at least.
First go here..http://forum.xda-developers.com/showthread.php?t=1426502 follow the instructions.... install universal naked drivers....
next go here.....http://forum.xda-developers.com/showthread.php?t=1774352 download and extract the file... you won't do the nvflash yet but it has a known good copy of adb in it....
next go here....http://forum.xda-developers.com/showthread.php?t=1615990 download twrp and follow the instructions to do a fastboot install..
At this point you should have a working twrp recovery, this is the one you should have had in the first place....
Now download a rom.... EOS JB or androwook will do.
Next now this is important....
Open the nvflash directory so you can see adb.exe, put the rom you downloaded into the folder at the same level (directory) as adb.exe now press and hold the shift button, right click (in the window where adb.exe is) and select open command prompt here.
Now type in the command prompt abd devices, you should see your transformer... if you do then type adb push /name of the rom/sdcard/ this will take about 5 minutes... for the name of the rom I usually right click and go to properties and copy the name.. in the command window you need to right click and paste (control v doesn't work) make sure you end the name of the rom with .zip.
Once that is done you should be able to go to install in twrp and your rom should install....
IF you have an external sd card, you can put the rom on it and insert it because twrp will read external cards and you don't need to do the adb thing.... let me know how it turns out.. even if you want to pm me..... good luck
Hey there,
I had the exact same issue. I too can fastboot to CWM but if I attempt to coldboot the OS I get the black screen of death. I managed to use the fastboot command to install the twrp to my prime. However, the Prime is not being recognized when I use "adb devices" in the commands, even though it successfully took the fastboot command that installed the twrp file. So I am stuck on the stage of trying to push the rom to my device. I know I am inputting the command successfully since I am getting an error: device not found on the return.
Any input would be greatly appreciated Gage. Thank you!
Update: I already had the CM10 nightly present on the device. So I selected to flash that, and it went through the normal processes. Wiped cache/dalvik at the end and rebooted device... am now again staring at black screen of death. It booted into the new TeamWin twrp recovery, which gave me a slight glimpse of hope...
I wish I could push the thanks button a thousand times! A few hours of working on these instructions (thanks to newbness and Windows 8), I finally have a working tablet again! You're the best Gage. Hunter, sorry I can't help, I used a Micro Sd instead of ADB.
Lazred if you would be willing to share your wisdom with me I would be most thankful, I would willingly run out and purchase a microsd card if it would mean the return of my beloved Prime =(
Funny that we had an issue with the same ROM (CM10 Nightlies). I tried reinstalling that several times with no avail. Since you can get into twrp, you should just be able to put that sd card into your computer (assuming you have an sd card reader) and load on another ROM (I used EOS 3 JB). Now, after you put that loaded micro sd into your tablet, you should be able to load up twrp, choose install, choose use external sd card, then pick the new rom to install and if you're lucky like me all your problems will be solved! Good luck!
Yea, ADB isn't working I had the same problem. Had to go get a micro sd card and use the latest TWRP. Thanks CM for the bum rom....
HunterofNittis said:
Hey there,
I had the exact same issue. I too can fastboot to CWM but if I attempt to coldboot the OS I get the black screen of death. I managed to use the fastboot command to install the twrp to my prime. However, the Prime is not being recognized when I use "adb devices" in the commands, even though it successfully took the fastboot command that installed the twrp file. So I am stuck on the stage of trying to push the rom to my device. I know I am inputting the command successfully since I am getting an error: device not found on the return.
Any input would be greatly appreciated Gage. Thank you!
Update: I already had the CM10 nightly present on the device. So I selected to flash that, and it went through the normal processes. Wiped cache/dalvik at the end and rebooted device... am now again staring at black screen of death. It booted into the new TeamWin twrp recovery, which gave me a slight glimpse of hope...
Click to expand...
Click to collapse
You do know that adb commands don't work from fastboot? So if you are trying them from the same place as where you installed twrp it is not going to work.
adb should work when you are inside twrp tho.
Have you tried installing the naked drivers and then going into twrp and trying adb devices?
flumpster said:
You do know that adb commands don't work from fastboot? So if you are trying them from the same place as where you installed twrp it is not going to work.
adb should work when you are inside twrp tho.
Have you tried installing the naked drivers and then going into twrp and trying adb devices?
Click to expand...
Click to collapse
Hi everyone I just wanted to provide an update. I can confirm that the CM nightly must have been bugged since it remains the only rom that continued to give me BlackSOD regardless of md5 checks, etc. I successfully flashed EOS from twrp. Booted fine, smooth as silk, all sorts of victory dances going on over here. In case anybody else stumbles upon this thread, I wanted to throw out a few more things elaborating upon the instructions of Gage, since for me at least the whole driver and push command thing was far more complicated than I would have wanted for anyone else.
When Gage says install the drivers, this proved very problematic for me. Thankfully there is a bundle out there, search the XDA forums for a file called adb-fastboot-win. This has your fastboot.exe in it. You are going to need this for step three. When you go to open the command window, shift clicking in the window in the directory file (folder) didn't work for me (win 7 ulti 64 bit). Instead, shift right click on the folder itself where your fastboot.exe and adb files are. That will yield your command window. Then follow the instructions as listed in the third thread provided by Gage. The fastboot command is quite simple.
Make sure you place your new twrp (Team Win Recovery Program) file in the same folder as your fastboot.exe, it does not actually have to be in the same folder as adb from what I have read and spoken with devs about, but fastboot.exe and adb should be in the same folder anyways. Make sure its in there, and use the command function to send it to the prime while its in usb fastboot.
I can confirm at this time that nobody seems to have an adb solution to this. Adb doesn't work in fastboot as flump pointed out, and adb wasnt functioning in twrp for me. Drivers were correctly installed, it could push to phone fine, issue was definitely with the Prime since it wouldn't show up under listed devices.
THE SOLUTION: As others have said, call a friend or go down to best buy (ugh overpriced) and get a measly 2gb micro sd card if you want the bare minimum and get the reader. Mount SD card in computer. Stick ZIPPED NEW ROM on sd card. Plug sd card into Prime. Boot into TWRP (just a reminder its power button and volume down, then press vol up when prompted) and select install, select button that says external sd, select zip, then select your GApps file, swipe to confirm flash, and pray to whatever higher power you believe in.
Hope this helps anyone else out there, and thanks so much to Gage and everyone else I consulted on the matter. I learned a lot during the process.
Related
Hi, I've had lot's of problems with my HTC recently, no adb access etc, device not being recognised and recovery playing up, ie not being able to wipe install roms etc... however I fixed the recovery issue and managed to do a nandroid backup, I put on I think it was 1.5 HTC sense hero rom... and recently realised that i can only flash 1.5 roms, not 2.1 anymore? would any developer know what would of caused this problem? Any 2.1 rom just locks on the Hero logo, and I've left it for over an hour in some cases and nothing happens. Again, I used to be able to put on any custom rom.... I'm all out of ideas.
wipe
did you wipe? what recovery image you using etc etc?
1. post in the correct section.
2. remove the ext4 partition from your sdcard, or change it to ext2 or ext3.
3. get adb logcat, otherwise this is like the question "my car won't run, can anybody tell me why?"
I have wiped numerous times... sorry for the "my car won't run type question etc...." just that I've done my research, gooogled, posted detailed info previously on here and another forum, I even fixed my own problem of the recovery image, without fixing that I would have nothing. But anyway the card is partitioned with swap, ext2, fat32 using the latest Amon_Ra image 1.6? something... i've spent weeks trying to resolve this and learnt a lot along the way.
Obviously not where to find the adb logcat... don't worry I'll google it.
Apologies for posting in the wrong forum, if it can be moved could a mod do so?
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Thanks for your reply, I will approach this method again at some point and give it a try, but I think I read somewhere that I couldn't do it for whatever reason, but I'll look into it again seeing as you've had the same issues. Thanks.
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Actually I believe I didnt attempt this because I was no longer able to get my HTC hero working with ADB, as soon as I plug the device in, it comes up as device unrecognised, so I think goldcard method it out.. :-(
on the risk of offending you again (even though i am trying to help here...): you did not provide really much valid info. for most things you just said "doesn't work". what happens if you start by pushing home+power? saying the recovery doesn't boot up tells what does NOT happen, for a diagnosis we need the info what DOES happen.
anyway, if i get you right your recovery is now working. now repartition your sdcard (ext2 and fat, NO swap), do a full wipe, then install the rom you desire to use, then move the log to sdcard ("other" in recovery). reboot your phone and execute "adb logcat > c:\logcat.txt" on your pc. if it doesn't boot up after five minutes stop logcat with ctrl-c and post the two logfiles (recovery.log and logcat.txt). you need to set up adb, if you have problems with that sort them out, there is no way to get any information about your problem without the log.
oh, and about the goldcard: i don't know too much about goldcard'ing, but i can't see how this should help here. my strongest guess is that the swap partition interferes with the boot process...
No worries no offence taken. Pushing Home+Power works and takes me to recovery. Back+Power takes me to bootloader and USB Bootloader device is recognised, so I am able to get Fastboot.
Just recently installed stock rom, to see if that solved the USB and ROM issues but no such luck, re-rooted, put anom latest recovery back on, and went on to do what you have advised to help.. i've attached only the recovery.log in zip format only, as when doing adb logcat command use mentioned(after installing new rom), all I get is "waiting for devices" whilst the phone is stuck on the Hero logo, I waited about 10 minutes, exited from the adb, and the log file was empty as I guessed. I've tried every possible way that I found on the web to try and get the ADB function working again and I realise this is important to get some info.. but I've ran out of ideas for that.
Maybe the recovery(attached) may show something, all I noticed is that the cache and something else was not wiped for some reason? If you or someone has time, have a look through maybe someone knows what is going on.
Thanks for your help and patience
Hello! I recently got a replacement for my Optimus V. It was having signal and SMS problems, so they decided to send me a replacement. I noticed this replacement has android 2.2.2 froyo pre-installed. so the first thing I tried was to root it with Rom Tools, but it didn't work, so I looked around and found Gingerbreak. Rooting was successful, and i had SuperUser privileges. So then I tried installing a custom recovery with RomTools, and it still told me I wasn't rooted. So then I tried Rom Manager, and it notified me the custom recovery was flashed, so i rebooted, and i just get a back-lit black screen. So then I tried booting into the bootloader, and it just boots to Android again, any idea why this is happening? Have they locked the bootloader?
I hope not, but that would I explain why I haven't been able to root my wife's "new" replacement phone.
Success!
Finally got my wife's phone rooted using GingerBreak. Restoring her apps (via TiB) as I type this.
FYI, I basically followed these steps: http://forum.xda-developers.com/showpost.php?p=13170826&postcount=171
RKBA said:
Finally got my wife's phone rooted using GingerBreak. Restoring her apps (via TiB) as I type this.
FYI, I basically followed these steps: http://forum.xda-developers.com/showpost.php?p=13170826&postcount=171
Click to expand...
Click to collapse
Not all phones are created equal. Make sure you have a stock 2G SD card formated to the default settings It gets really picky about the sd card some times. The more stuff on your sd card the longer it will take. Turn on USB debugging,your not going to plug it into your PC,but you need to have it enabled or the exploit wont work. Make sure you have a good file manager like Super Manager installed on your phone. Download the Gingerbreak.apk. With the file manager go to sdcard/downloads or download. Move the exploit to the root of the sdcard(somewhere near the bottom of the list of folders). Open up the exploit and select install. Once it's done installing the exploit to your phone select done,exit. Reboot phone. Go to app draw and select the exploit,select run. It might take up to 10 min.for it to run. If it goes 12min.pull battery and try again(it could take several tries). You must reboot after every failed attempt. If you get an error message it does not like your SD card. Reformat to default settings using you computer and try again. If you are using a sd card that is not 2G it might not work. Once it reboots and you are looking at your home screen,you are rooted. Now go to the market and download Busybox installer. With a file manager go and check where su has been installed. It's either /system/bin or /system/xbin. Install Busybox wherever su is. Go back to the market and update Super User. Gingerbreak will not install the proper flash_image to flash a custom recovery, but, You can use ROMTools to flash Xionia recovery,or ROM Manager to flash ClockworkMod recovery. Once you have a custom recovery on your phone you need to make a nandroid backup of your system because now that your ROOTed you now can delete things you may not want to, then it's to late. AHH, But you made a backup that you can restore and your phone is as good as new again....P.S.Sorry no links, till I have 8 or more posts,at least I think that's what it said
awerni said:
Hello! I recently got a replacement for my Optimus V. It was having signal and SMS problems, so they decided to send me a replacement. I noticed this replacement has android 2.2.2 froyo pre-installed. so the first thing I tried was to root it with Rom Tools, but it didn't work, so I looked around and found Gingerbreak. Rooting was successful, and i had SuperUser privileges. So then I tried installing a custom recovery with RomTools, and it still told me I wasn't rooted. So then I tried Rom Manager, and it notified me the custom recovery was flashed, so i rebooted, and i just get a back-lit black screen. So then I tried booting into the bootloader, and it just boots to Android again, any idea why this is happening? Have they locked the bootloader?
Click to expand...
Click to collapse
With power on,pull sd card. Put your sd card into PC and copy(don't move anything off the sd card)the contents into a new folder. Put the sd card back into phone with power on. If it boot's up properly let me know. You should be able to power off and on and it boots up properly. Don't do anything more to it until you let me know(your going to have to change some permissions on some files, check Busybox install,etc.).
awerni said:
Hello! I recently got a replacement for my Optimus V. It was having signal and SMS problems, so they decided to send me a replacement. I noticed this replacement has android 2.2.2 froyo pre-installed. so the first thing I tried was to root it with Rom Tools, but it didn't work, so I looked around and found Gingerbreak. Rooting was successful, and i had SuperUser privileges. So then I tried installing a custom recovery with RomTools, and it still told me I wasn't rooted. So then I tried Rom Manager, and it notified me the custom recovery was flashed, so i rebooted, and i just get a back-lit black screen. So then I tried booting into the bootloader, and it just boots to Android again, any idea why this is happening? Have they locked the bootloader?
Click to expand...
Click to collapse
With power on,pull sd card. Put your sd card into PC and copy(don't move anything off the sd card)the contents into a new folder. Put the sd card back into phone with power on. If it boot's up properly let me know. You should be able to power off and on and it boots up properly. Don't do anything more to it until you let me know(your going to have to change some permissions on some files, check Busybox install,etc.). If it doesn't work,you can try something else as well.EDIT: Try and see if your phone is still recognized by your computer. It might be,if it is then open up ROMTools and select ROMTools.exe . Type in 2(enter). Type in 2 (enter) Allow SuperOneClick to establish a Shell Root(temporary Root)click ok and close small window but not SuperOneClick. Click on command prompt window to bring it to the front. Type in 4(hit enter key). Let it do it's thing. If it was successful it will say so. Now try and pull SD card out with power on. Put SD card back in with power on.
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
babybear293 said:
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
Click to expand...
Click to collapse
can't do commands via usb, i'm reading this to mean, you don't have adb access.
after wiping the /data partition, where system settings are stored, including the toggle for adb access via, you will probably have to re-enable.
to enable adb access via usb on sense -> settings -> applications -> development -> usb debugging. this should be toggle on.
if that doesn't work, post back and we can start digging deeper but i'm hoping that'll resolve your isse!
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
thos25 said:
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
Click to expand...
Click to collapse
Well there is a lot going on in that post ... Not sure how my application Flash Image GUI failed. I would be more than happy to fix/resolve any bug or issue you've encountered!
Fastboot usb mode should always work. There is no setting in Android which will have any impact on fastboot usb mode (other than not allowing the device to boot into the bootloader). I generally find the best process to be, boot the device into the bootloader, plug in usb and then select fastboot.
Perhaps, once you're in the bootloader, you can also select fastboot and then plug in USB (this works best on my NS4G).
Either way, fastboot usb should always work. If you're using Windows, there could definitely be a drivers issue or Windows being finicky with the drivers and that might result in fastboot USB not working. A simple reboot of the Windows machine should clear any fastboot driver issues.
The best working method to correctly load a ROM is by properly loading the recovery to work with the HTC unlock method. HTC unlock method will only grant the recovery write access to the boot partition when the recovery image is temporarily fastboot boot'd. The command is: fastboot boot c:\android\cwm-recovery.img.
If you boot into the bootloader and select recovery from the menu, it will boot into the recovery, but the HTC unlock method will not grant the recovery write access to the boot partition. You can flash a ROM from here and restore a nand. Both will completely successfully and claim they flashed the kernel w/o any issues but the memory write lock will have prevented the kernel writes from being retained.
Also, regarding my application, Flash Image GUI, it should properly flash any EVO 3D kernel .zip file from normal Android mode as the HTC unlock method allows kernel write access while in normal Android mode.
Why did HTC block kernel write access from recovery mode? They haven't provided an answer .. we can only speculate ...
Hope that helps explain a few more steps to the process and provide greater clarity!
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
thos25 said:
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
Click to expand...
Click to collapse
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
I had a similar issue when i was switching to AOSP kernels/roms. I rebooted my phones once or twice and it connected fine. Maybe it have something to do with AOSP since MIUI is aosp also.
joeykrim said:
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
Click to expand...
Click to collapse
Thanks for the comments and lesson. I apologize for not responding sooner, but a recent death in family prevented me from really being on here too much lately.
1) I pretty much figured that. Yeah. I only try to flash using this method, that is why when my fastboot USB disapeared I thought I was really in a bad spot. Luckily I got it working again, so all was not lost.
2). Yes. I know it should remain on SD card, which was strange why I couldn't find it. However, thinking back on it, I do remember deleting some files off of my SD card on the same night. I probably just mistakenly deleted my CWM Recovery with my NAND backups. Sometimes when I double click a file to look at it, when I leave the file I see that there is a checkmark on that file. I may have just not noticed the checkmark on the CWM, went to delete another file, and mistakenly deleted CWM with it.
3) An RUU will not change a RADIO? I was under the impression that they did. Sort of like applying an OTA, but manually doing it through SYNC.
well, thanks again though. I learned some new things and appreciate it.
Flash image GUI works like a charm
Sent from my PG86100 using XDA App
i m a newbie
plz tell me how to get out of the fastboot usb mode. i m stuck with the G1 screen having fastboot usb title on the top.
PLZ HELP!!!
Not sure how, and more importantly, how to fix it. Previously, I unlocked with the Asus tool, did the sparky root method, installed the most current Prime version of CWM, then flashed JellyBro. Wanted to flash a new ROM last night. I booted into CWM and tried to do a backup, but got some kind of error about not being able to back up the boot image, or something like that. Not wanting to flash a new ROM without a backup, I just restarted, but now it just sits on the EEE Pad splash screen. If I hold down the power button, it restarts but still stays on the splash screen. I had to hold down the power and both volume buttons for a long time to get it to turn off and stay off without restarting. So, what do I do?
mrw1215 said:
Not sure how, and more importantly, how to fix it. Previously, I unlocked with the Asus tool, did the sparky root method, installed the most current Prime version of CWM, then flashed JellyBro. Wanted to flash a new ROM last night. I booted into CWM and tried to do a backup, but got some kind of error about not being able to back up the boot image, or something like that. Not wanting to flash a new ROM without a backup, I just restarted, but now it just sits on the EEE Pad splash screen. If I hold down the power button, it restarts but still stays on the splash screen. I had to hold down the power and both volume buttons for a long time to get it to turn off and stay off without restarting. So, what do I do?
Click to expand...
Click to collapse
Looks like this could help: http://forum.xda-developers.com/showthread.php?t=1662158
Next time I recommend using TWRP and not CWM.
qery said:
Looks like this could help:
Next time I recommend using TWRP and not CWM.
Click to expand...
Click to collapse
Yeah, people have been recommending ditching CWM for TWRP to me for a little while, now, and I continued sticking with it because I was so familiar with it and didn't want to bother with anything else. Didn't know there was a problem with the current version for the Prime. But yeah, I think I'm definitely going to make the jump to TWRP if/ when I get my Prime back up and running.
The biggest issue for me is, I'm not very familiar with actually using ADB/ command prompts for any of this stuff. Every device I've unlocked/ rooted, I used an automated script to do it, so I didn't have to bother with any of that. I also did read over the stuff about nvflash, but I couldn't really make heads or tails out of the instructions, so I thought it'd be best for me to not tamper with it. Figured I was playing safe with my Prime, so I wasn't concerned, anyway.
I believe I can still access fastboot on my Prime (I don't technically know what "fastboot" is or does, though); if I power it on holding down the power and volume down buttons, I get three options (wipe data, fastboot USB mode, and reboot), but I haven't tried connecting it to a computer yet. I'll take a look at your link.
Hm. So from what I gather, I need to get a new blob file; the one in the link you provided talks about getting it from the Virtuous Prime ROM, but the reason this concerns me is, VP seems like a stock ROM, and the unbricking thread notes that if you apply a stock blob file after installing CWM, you get an unrecoverable brick. So... not sure if I should use the Virtuous Prime blob file, or what? I don't want to permanently break my Transformer Prime. :/
mrw1215 said:
Hm. So from what I gather, I need to get a new blob file; the one in the link you provided talks about getting it from the Virtuous Prime ROM, but the reason this concerns me is, VP seems like a stock ROM, and the unbricking thread notes that if you apply a stock blob file after installing CWM, you get an unrecoverable brick. So... not sure if I should use the Virtuous Prime blob file, or what? I don't want to permanently break my Transformer Prime. :/
Click to expand...
Click to collapse
Gosh.... Stock blob = Asus blob downloaded from Support Center...
Just follow the instructions.
Striatum_bdr said:
Gosh.... Stock blob = Asus blob downloaded from Support Center...
Just follow the instructions.
Click to expand...
Click to collapse
Oh, okay, so the VP blob isn't "stock" then? I guess I'll give it a whirl then. Probably tomorrow, though, as I don't have much time today.
I'm not so sure I've set up fastboot on my computer correctly... I followed some instructions on a random site I googled, but I don't know if it worked. I put my Prime in fastboot mode, and when I connected it to my computer, Windows found and downloaded a "Fastboot" driver. But when I opened a command prompt and entered "fastboot devices", nothing happened.
Ok you sould use Universal Naked Drivers from developer forums.
VP is based on stock rom, but it is made for unlocked devices, so it does not hardbrick you (I think it doesn't flash bootloader).
You need to have files Android Platform Tools (from Android SDK) installed (or copied in folder). To this folder you copy files needed to be flashed (mine is c:\program files (x86)\android\android-sdk\platform-tools\). Then you open cmd from there (in explorer press Shift+Right click and select Open command window here).
Now reboot tablet while holding VolDown and select Fastboot (usb icon). Next connect to pc.
After that you should be able to use fastboot commands.
Sent from my Transformer Prime TF201 using Tapatalk 2
Okay, thanks everyone, looks like I'm back up and running!
Just a question; am I reading it right that with the newest version of TWRP, you can't do backups and restores without having done that nvflash thing?
Hm. This is probably unrelated, but... I'm not sure TWRP is working correctly. I installed it via GooManager after I got back up and running (I had tried to flash it via fastboot when unbricking, but for some reason, it didn't take, and I was still on CWM). Anyway, in TWRP, when I do my wipes, it doesn't appear to actually have any effect, even though it goes through the process and says they were successful. Also, when I try to install a ROM, the zips don't appear on the sdcard folder in TWRP, even though they are, in fact, on there.
Putting them on an external card allows TWRP to see them and flash them, but because TWRP apparently isn't actually doing the wipes (even though it says it is), I'm having trouble flashing other ROMs (because I'm basically "dirty flashing" from Virtuous). In particular, I'm trying to flash Blackbean; after the boot animation, it goes through the "Android is upgrading" thing for what I assume is still the Virtuous Prime stuff, then I get an error about system.media (something like that) not responding, and then it quickly goes back to the boot animation and continues to loop from the aforementioned error to the boot animation over and over until I force turn the tablet off.
Anyone know what the heck is going on? Why does it seem like TWRP isn't actually wiping the tablet, and why is it not recognizing the zips in the internal sdcard folder?
mrw1215 said:
Okay, thanks everyone, looks like I'm back up and running!
Just a question; am I reading it right that with the newest version of TWRP, you can't do backups and restores without having done that nvflash thing?
Click to expand...
Click to collapse
Yes. If you don't want nvflash, use older version - in OP it says that 2.2.1+ needs nvflash bootloader.
mrw1215 said:
Hm. This is probably unrelated, but... I'm not sure TWRP is working correctly. I installed it via GooManager after I got back up and running (I had tried to flash it via fastboot when unbricking, but for some reason, it didn't take, and I was still on CWM). Anyway, in TWRP, when I do my wipes, it doesn't appear to actually have any effect, even though it goes through the process and says they were successful. Also, when I try to install a ROM, the zips don't appear on the sdcard folder in TWRP, even though they are, in fact, on there.
Putting them on an external card allows TWRP to see them and flash them, but because TWRP apparently isn't actually doing the wipes (even though it says it is), I'm having trouble flashing other ROMs (because I'm basically "dirty flashing" from Virtuous). In particular, I'm trying to flash Blackbean; after the boot animation, it goes through the "Android is upgrading" thing for what I assume is still the Virtuous Prime stuff, then I get an error about system.media (something like that) not responding, and then it quickly goes back to the boot animation and continues to loop from the aforementioned error to the boot animation over and over until I force turn the tablet off.
Anyone know what the heck is going on? Why does it seem like TWRP isn't actually wiping the tablet, and why is it not recognizing the zips in the internal sdcard folder?
Click to expand...
Click to collapse
Try using older version of TWRP.
And in case of problems, report in twrp thread with a logcat.
Hey everyone, thanks in advanced for looking.
I purchased a rooted HTC 4g View and it was running stock GB with S-OFF. It was rooted with Revolutionary.
I decided it was time to upgrade to HC but I had no knowledge of flashing roms or anything like that and hired someone to do it for me. From what I can tell he flashed "Desenced" and it was great! Then the problems started..
The tablet every so often just went to the loading screen of HC start up. It started doing it very rarely to every hour or so and I decided I would just buy another table because of the inconstant behavior.
Now the tablet won't turn on unless plugged in and only boots into ClockworkMod Recovery v5.8.1.5
When I try to wipe everything and reflash desenced, it says Flash Complete! Then reboots, goes straight to CWM again.
I've tried using command prompt while the tablet is plugged in but no matter what I mount, it won't respond to the computer.
Please help, I'd love to have this tablet back.
Okay I found the solution!
I used the adb and the drivers for the stock rom (3.2) from sdk manager.
In CWM Recovery I mounted /system in order for my computer to recognize the tablet.
Once there, I kept rebooting the tablet using the command, "adb reboot oem-78" until the corrupted rom booted up enough for me to be able to use the RUU.
I then followed the instructions on this thread
Everything is now great and I've learned a lot. Thanks everyone for looking and if anyone has any questions, I'd be more than happy to share.
Cheers!