both doing it manual and fresh kitchen tell me i cant load the recovery image... Does anyone know anything that can be wrong??
I don't know if this will help, but I had the same problem and I just tried loading the image from recovery about 8 times, then it worked.
xxxk15 said:
both doing it manual and fresh kitchen tell me i cant load the recovery image... Does anyone know anything that can be wrong??
Click to expand...
Click to collapse
IF you follow this set of instructions, you'll get it.
DO NOT skip any steps.
http://forum.xda-developers.com/showthread.php?t=583291
Thanks,
Bubba
xxxk15 said:
both doing it manual and fresh kitchen tell me i cant load the recovery image... Does anyone know anything that can be wrong??
Click to expand...
Click to collapse
Double check recovery image name in SD root. I know it sounds stupid, but when I first tried to somewhere in the cut/copy from my computer to the SD card it put a (2) in the file name.
recovery-RA-heroc-v1.5.2(2).img
instead of
recovery-RA-heroc-v1.5.2.img
now it finally went though but when it boots into recovery. an exclamation mark comes up. what is wrong now?? and this is my second phone rooting if it means anything
Do you have a Sprint Hero? If not then none of these methods are going to work for you.
If you do then run the auto-rooter in the newest kitchen (1.0.5.3) with debugging turned on and put the output on pastebin.com for me.
You booting in to the exclamation point picture shows that RA didn't install properly.
what does this mean "and put the output on pastebin.com" and yes i have a sprint htc hero and yes i used the manual way to root and auto rooter and it wont boot into recovery
xxxk15 said:
what does this mean "and put the output on pastebin.com" and yes i have a sprint htc hero and yes i used the manual way to root and auto rooter and it wont boot into recovery
Click to expand...
Click to collapse
Have you tried turning your phone off and holding down.. Home + power button.. to boot into recovery?
Pastebin.com is a place to post your code.. The you put it gives you when it doesnt work. Highlight and copy it and paste in in pastebin.com and then copy the web address it gives you and post it here.
Jus10o said:
Have you tried turning your phone off and holding down.. Home + power button.. to boot into recovery?
Pastebin.com is a place to post your code.. The you put it gives you when it doesnt work. Highlight and copy it and paste in in pastebin.com and then copy the web address it gives you and post it here.
Click to expand...
Click to collapse
As Jus said... turn on debug mode in the kitchen (under help tab) and then go run root. In the debug window for the kitchen there is a button that will link you to pastebin.com. Copy the results of the debug window to pastebin.com and submit it. Then provide the url to that pastebin so that I can see the results. There's no reason it should be failing. Make sure you are using kitchen 1.0.5.3 as it had updates to the rooter.
http://freshkitchen.pastebin.com/gScaZ7Wk
what does this mean??
Is that all that it shows when you click on "Root" to root your phone?
no this is what it says
http://freshkitchen.pastebin.com/VSjvea0u
i dont know waht to do??
DOO THIS...
Download this here... http://rapidshare.com/files/360227978/recovery-RA-hero-v1.6.2.img
Then mount your sdcard to your computer and put it on the sdcard.. DONT PUT IT IN A FOLDER Just on the sdcard
Go to start on your computer.. and run "cmd".. or command prompt and navigate to your c:/androidsdk/tools folder.. OR the place yours is located.
Then type these commands
adb shell
su
cd /sdcard/
flash_image recovery recovery-RA-heroc-v1.6.2.img
reboot recovery
ORRRR DO THIS
On the Fresh Kitchen screen go to ROOTER tab.. Click on "Flash RA 1.2.3 older version".. Then click root your phone.
Not sure if you've had any success yet...
My gf wanted me to root her phone as I did it to mine and got it done no problems in 15 minutes. I went to do hers and for the life of me I could not boot into the recovery image. I tried everything including some of the various ways to do factory resets and nothing worked. I was pretty frustrated. What finally worked for me was googling Sprint RUU and running that. It's an executable file that requires the phone to be plugged into your PC via USB. I ended up flashing hers to 1.29.xxx whatever and after that it rooted fine. I had a custom and theme and 2.1 installed in 15 minutes after that.
fortyozspartan said:
Not sure if you've had any success yet...
My gf wanted me to root her phone as I did it to mine and got it done no problems in 15 minutes. I went to do hers and for the life of me I could not boot into the recovery image. I tried everything including some of the various ways to do factory resets and nothing worked. I was pretty frustrated. What finally worked for me was googling Sprint RUU and running that. It's an executable file that requires the phone to be plugged into your PC via USB. I ended up flashing hers to 1.29.xxx whatever and after that it rooted fine. I had a custom and theme and 2.1 installed in 15 minutes after that.
Click to expand...
Click to collapse
I updated my post above you for the instructions to get the newest recovery to your her phone... flipz thing might be putting the new 1.6.2 on the sdcard and then trying to flash v1.2.. I think thats what its showing.
the command "flash_image recovery recovery-RA-heroc-v1.6.2.img" was not found so i put it in as "flash_image recovery-RA-hero-v1.6.2.img" is that ok... but it still didnt work.. now i am going to try the auto rooter
i tried the auto rooter and it didnt work either..
Related
Hi guys,
I was trying to unroot my nexus S using the guide found here (http://forum.xda-developers.com/showthread.php?t=1088494&highlight=unroot)
After clicking start on odin, it started to do its thing and then it failed all of a sudden. and now im stuck on the yellow triangle Downloading screen. I press and hold power nothing happens. i dunoo what to do. I am a complete noob. someone please help. I am attaching the image of the what the screen looks like (http://postimage.org/image/3dhtlidg/)
and here what odin looks like now (http://postimage.org/image/3eqh3vpg/)
ok guys, i took out the battery and put it back on and turned it on again and it powered on but now i have no signal or empty bars. it shows aeroplane now.. i tried different sims no difference.. i get no service.. i think this odin fail at radio damaged my radio somehow..someone please advise me.. please .. i did volume up button + power and tried to go to recovery but i get triangle with exclamation mark. so i took out the battery and reboot it to normal. no signal. just the aeroplane icon. Also when i put the phone in USB mode, i see folders like clockworkmod and im able to see my back up that i made before doing all this. However not able to access it in the phone. I also see that all my apps and everything is gone, but i still some apps folders in the usb mode. what should i do?
First, your link goes to a NxS 4G guide, but you state you got a NxS (non-4G). Which one you got?
Following is for the __NxS only__ (as I have no experience with the 4G):
If a little Droid is holding the "triangle with exclamation mark" then that is normal as you're accessing the stock recovery, press vol up + power again to see the recovery.
Once done that go here and get a full rom flashable zip for your device. Get a "signed" version if available as those are flashable via stock recovery. (*) Put the zip on your sdcard, reboot into recovery again, wipe everything the options allow you to, install zip from sdcard, reboot. You're done with an unrooted, stock phone.
If there's no "signed" you gotta flash the cwm recovery via fastboot first (USB drivers seem to be working and your phone is recognized). Go mount and storage and choose "Mount USB storage" Then continue after the (*) and leave out the reboot after putting the zip on your sdcard.
yeh crap i just realized.. i used the guide for nexus s 4g.. i have the gsm model (non-4g). from here in canada. damn i feeel so stupid... fml..
ok so behind the battery the sticker says my phone model is I9020A and then I went to the page yu asked.. and i found the following two of interest.
Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader
Works on: I9020A
Unofficial, unsigned, must flash through ClockworkMod Recovery. Contains recovery, radio and bootloader.
Courtesy of XDA forum member scott8281
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
My phone before all this mess occured was on GRJ22 build. So can i use the 2nd one here since its official and signed whereas the first one is unsigned. and like u suggested i should try to find a signed rom.
next question, how do i "wipe everything the options allow you to" ..
also when i do vol up + power and scroll to recovery and press power.. google logo comes up and then the droid with white triangle that has exclamation mark. I just cannot load into recovery :$
sorry for being so noob at this :$ But thanks for helping...
Breathe.
No, you cannot use the second flash "Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader" This is not for the I9020A variant.
I can tell you how to get everything back to stock. Are you willing to unlock the bootloader? There is no full signed rom for the I9020A.
You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.
Oh okay. yes please I am willing to do anything to get this phone working to normal. and by the way, when i do volume up+power, i see locked stated - unlocked. doesn't that mean my bootloader is already unlocked. I also see the lock icon along with google when i turn on the phone.
cool6324 said:
You need to:
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide#Unlocking_the_Bootloader
http://wiki.cyanogenmod.com/wiki/Ne...de#Installing_the_ClockworkMod_Recovery_Image
Then install
http://forum.xda-developers.com/showthread.php?t=1033269
Then update back to 2.3.4
http://android.clients.google.com/p...5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip
Then lock the bootloader.
Click to expand...
Click to collapse
okay so basically i start following the guide from the point it says Installing the ClockworkMod Recovery Image since my bootloader is already unlocked.
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
also for flashing cyanogen mod, i would choose the "method via recovery" right since my phone is not really rooted right now. I don't have the ROM manager app. Thanks a lot cool6324
The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
one question though, right now when i connect my phone through usb, i am able to see the folder such as clockworkmod in sd card, so if im installing clockworkmod recovery, am i just reinstalling this again?
Click to expand...
Click to collapse
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.
rentaric said:
The rom has to be for your phone. If your phone is an i9020A you got to take the first one you marked red.
@cool6324, I think his phone's bootloader is unlocked as his phone was rooted before and later then 2.3.x, means no Gingerbreak to avoid unlocking the bootloader.
---
forpulse, you got ADB set up and ready to go? (If not go to: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ to learn how to set it up)
If yes, download the rom to your pc. Also download the cwm recovery here. Boot phone into Android. Copy the rom on your sdcard (needs to be in the top folder). Copy the cwm recovery into the \tools (see below, (*))
Keep your phone connected via USB to your pc. Unmount the sdcard (the Droid got to be green not orange anymore), make sure you activated "USB Debugging" in settings (not sure of the right english terms should be in: "Apps/Programs" > Development). Now start a command prompt (windows key + r, then type "cmd", hit enter). (*)Navigate to the \tools inside ADB/SDK folder you created already or created by following the unlockr guide I linked above. To navigate simply type "cd <drive letter>:\<folder name>\tools and confirm with enter. Once inside the right folder you can start using the following commands:
adb devices (this should return you your device's id)
adb reboot bootloader (this takes a few secs and your phone will boot into bootloader menu)
fastboot flash recovery <recovery image name>.img (this should return a time and an "OK")
Now you can continue on your phone:
Navigate into recovery
Wipe > Factory reset, cache and dalvik cache
Mount and Storage > format system/boot
Install zip from sdcard, choose the ROM's name, install, confirm
"Go back" until you can choose "reboot system now", phone should boot into unrooted, stock Android now.
---
That clockworkmod folder contains so called "Nandroid backups". This contains a full backup of your phone (__if__ you made one).
Did you make one before messing up your phone? If yes, follow my guide above to the point your going into recovery and just hit "backup and store", "restore" instead of flashing a new rom. I'd recommend to "wipe" "factory reset", "cache" and "dalvik cache" before though.
Click to expand...
Click to collapse
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand. Also, when i go to download the CWM recovery. it says NS4G, so is this again for the sprint 4G model? or it also works on non-4g model which is what i have. I am just confirming this since I don't want to make the same mistake as above. :$
forpulse said:
Yes, i do have ADB set up ready to go but if I understood your right. Do I follow what your saying after following cool6324's guide or don't follow that and do what u suggest. I have not yet started out on his suggestion as I was reading everything and trying to understand.
Click to expand...
Click to collapse
The linked guide's result is equal to mine if you don't flash the CyanogenMod, but the rom cool6324 linked. Just make sure you get a full rom for _your_ device this time
rentaric said:
Copy the rom on your sdcard (needs to be in the top folder). C
Click to expand...
Click to collapse
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...
forpulse said:
which top folder are u talking about. is it ".android_secure" ? and I don't extact the ROM zip file right? i just put that directly in "top folder" ? and just to make sure i'm using "Stock-GTJ61-I9020A-Unsigned"
(100mb) found from one of your earlier links.
When I went to download CWM recovery from ur provided link, I saw different ones.. is it only for colour different purposes or there is actually a valuable difference amongst them? or do i download them all... i sound so stupid right now asking such questions:$
I'm really sorry If I am frustrating you with these stupid questions.. i've only had this phones for 2 days and its my first time with android... but thanks again...
Click to expand...
Click to collapse
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App
rentaric said:
Good morning.
Yes, the difference between those recoveries is just color of text. !!Don't get the 4G version!!
The top folder is the one you access when the usb storage pops up on your pc. The zip file goes in there unextracted.
File size seems correct for a full rom.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Good Morning,
Alrighty, I think I have understood everything now, although, I'm at work right now so I will begin the process 8 hours later today and get back to you with the results... thanks for being so patient...
Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..
forpulse said:
Hey rentaric,
i followed your guide and im delighted to say that my phone is back to normal or at least i think so lol.. everything is worked out and so far the phone is running fine. i made calls and what not.. the only issue i got now is... auto-rotate does not work. i cannot type text in landscap mode even though i got auto-rotate checked in display settings.. even in gallery, photos do not auto-rotate.. pretty much auto-rotate does not work whether i turn it on or off :S ..would you happen to anything about this? nonetheless, thank you so much for helping me out..
Click to expand...
Click to collapse
Glad to hear it worked out for you to some degree. Sadly I have no solution to the not workign sensor part. See, I'm not pro myself, I'd just try widgetsoid app first. It got an rotate on/off function in its widget, if that wouldn't work for me I'd prolly flash another rom to see if it's the sensor trying to bully me. In the end hardware failures are still a possibility even on teh NxS.
sounds good.. no worries... i have a feeling this phone might have a defective sensor since it did not work also before with the older ROM which was GRJ22 xxkd1 ... but anyway i'll search/ask around if anyone knows anything... thanks again man...
REALLY hope someone can help me, bout to flip out...My Asus TF101 received an update the other day that got installed, (5/3/12) , and as soon as ICS rebooted to apply update i get the laying down Android with red Gear (or exclamation point, cant remember).I turn off, back on, and it dumps me directly into ClockworkMod5.5.0.4,....I have manually tried to install other Recovery images, to no avail.. tried to do ADP push but am getting "cannot perform action: read only file system). Ran command to remount and reset file system to RW, whats weird is i can sit and watch the solarnz recovery unzip, validate, install, and say success (through CWM recovery)....then I reboot, as prompted after new image flash and 5.5.0.4 CWM REMAINS!! only way to get into ICS is vol - and power and wait for RCK mode and dont press anything..."Wipe Data/Android" screen appears and I can start ICS from there. I just want CWM GONE and my Tablet to start normally. I'd take back Stock in a heartbeat... Thanks to anyone that may be able to offer a little guidance.. Thanks!!
Ive the same problem here... everethong you listed and a plus that ive tried so many ways get rid of the CWM but nothing worked ... i dont know whatelse showld i do..
download the 4.0.3 ruu from here: http://forum.xda-developers.com/showthread.php?t=1631830
that should fix it
cheers
caiogustavo15 said:
Ive the same problem here... everethong you listed and a plus that ive tried so many ways get rid of the CWM but nothing worked ... i dont know whatelse showld i do..
Click to expand...
Click to collapse
If you can still get into CWM than you are GOOD..i WAS able to flash an old verson of CWM that supported externalSDcard support(cause 5.5.0.4 doesn't)..
cant find exact one. i sent TF101 to ASUS, RMA'ed my device..and they fixed it WITH SU and ROOT evidence probably everywhere. Tried to get rid of it but im sure they could find something. anyway, I justed adb pushed the older CWM rom , it was army greenish text and had far more options if that helps, support for extSD, 5.2 keeps ringing a bell..don't quote me though. then selected "install zip from sdcard" on your 5.5.0.4 and navigate to the folder you pushed it to with ADB..(if you need directions for pushing the rom lemme know) Wish i could remember for ya. Google "CWM android" under images and find the green looking one, maybe youll get the version number that way I have read that a C series bootloader unlocker for Transformer is about to be released... enabling NVflash to work on the device. NO MORE softbrick!!!! It took 6 months for the B series to come out, figured it would take about this long.
Solution to help totally screwed TF101G with CWM 5.5.0.4! Go into CWM, PC discovers "Transformer" device. I found in somewhere "1-Click Transformer Root_1.1" software. Find, download and unzip. Search manually driver in these folders, inc subfolders. Founds ADB bla bla bla driver... I copied folder "Source" to C:\ and started CMD in Start menu. Go to "Source with CMD. Write "adb start-server" "adb devices" and you could see device 12345.....! I tested command "adb pull /sdcard/ c:\ (or other order, but was smth like that). Old backup files was in C:\ like clockworkmod! And download .zip with full rom and do that:"adb push c:\myromwhateveritnameis.zip /sdcard/" and with CWM install .zip!
This technique worked on my 3 months bricked TF101G, that's why I registered today here and shared experience. And you do not have to replace your 5.5.0.4, because it is working solution.
I've gone through all the old posts, tried various suggestions using Odin and the SDK but without success.
My son got his Samsung GT-i5800 locked because he forgot the swipe code. I tried suggestions on forums but no good. So I put the phone into the recovery mode and selected "wipe data factory reset" then selected "system reboot now". The phone then rebooted and arrived back into the recovery menu. Everything I've done has brought me back to "Samsung Recovery Utils for BML"
I've downloaded the SDK manager and tried typing "abd" into the command line but it is not recognised. I've pointed the command line at the tools folder, then the platform-tools folder found the abd application but cannot run any commands. Not that it would do much good anyway as the phone doesn't connect to the PC via USB when in the recovery menu.
I know this problem has been mentioned before but all the suggestions from those posts have not worked. I have now run out of ideas.
I've spent too many hours on this, so before I go buy another phone, does anyone have any other suggestions, please?
thanks.
itsar1 said:
I've gone through all the old posts, tried various suggestions using Odin and the SDK but without success.
My son got his Samsung GT-i5800 locked because he forgot the swipe code. I tried suggestions on forums but no good. So I put the phone into the recovery mode and selected "wipe data factory reset" then selected "system reboot now". The phone then rebooted and arrived back into the recovery menu. Everything I've done has brought me back to "Samsung Recovery Utils for BML"
I've downloaded the SDK manager and tried typing "abd" into the command line but it is not recognised. I've pointed the command line at the tools folder, then the platform-tools folder found the abd application but cannot run any commands. Not that it would do much good anyway as the phone doesn't connect to the PC via USB when in the recovery menu.
I know this problem has been mentioned before but all the suggestions from those posts have not worked. I have now run out of ideas.
I've spent too many hours on this, so before I go buy another phone, does anyone have any other suggestions, please?
thanks.
Click to expand...
Click to collapse
^First of all, there's no such command called as "abd". Also, I'm pretty sure that you probably haven't installed adb properly. Just follow the steps given in the following tut to make it work:
[How To] Setup ADB for Windows/ Mac
And secondy, there's no need to go through all that hassle. Simply pull out your battery. Insert it back and then press the following key combo:
"Vol Down + Home + Power Key". This would take you to the Download mode, now simply flash any stock or custom ROM via Odin. Here's a list of Stock ROMs available for our device:
Galaxy GT-15801 ROM/KERNEL List
h4r5h said:
First of all, there's no such command called as "abd". Also, I'm pretty sure that you probably haven't installed adb properly. Just follow the steps given in the following tut to make it work:
[How To] Setup ADB for Windows/ Mac
Click to expand...
Click to collapse
Thanks for your suggestion. I will give it a go when I get some more time. I was following quite carefully what others had written in posts. I can only assume they missed out a detail that they thought was obvious.
h4r5h said:
And secondy, there's no need to go through all that hassle. Simply pull out your battery. Insert it back and then press the following key combo:
"Vol Down + Home + Power Key". This would take you to the Download mode, now simply flash any stock or custom ROM via Odin. Here's a list of Stock ROMs available for our device:
Galaxy GT-15801 ROM/KERNEL List
Click to expand...
Click to collapse
Sadly I've gone through all that. You are not the first to suggest this. I flashed the rom to the phone, Odin says "PASS" but the phone just reboots back in recovery mode.
It feels like that the phone's equivalent to the bios is telling it to go into recovery mode and not boot up the operating system. So regardless of what ROM is flashed onto the phone, I get the recovery menu. :crying:
Delete boot partition
And reflash...
Hope it will ... or else try purumod ..
Sent from my GT-I5800 using xda premium
If u were on stock rom initially then u can always get help from Samsung service center
Secondly if u have cwm recovery u can install rom or update.zip through cwm itself
Also
Its surprising that after data wipe such problem appeared did u miss out something
Sent from my GT-I5800 using xda app-developers app
hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again
any ideas please?? or am i completely out of luck?
When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
parkourgamer said:
Ok I finally got this tablet rooted using some chinese oneclick root tool worked great do to it was the only kit that was able to root it and i installed supersu apk to replace to chinese version worked and i went to update supersu and hit the twrp (not knowing what it was at the tim stupid right i know lol) and now it is stuck in the twrp/cwm bootloop and i cant get into recovery mode when i try it says updating img blah blah and restarts back into the bootloop. It is running 4.1.1 JB and has a micro sd card slot.There is a pic in the atachment because i dont know how to upload it to this post but it is just a pic no "extras" are included no viruses maleware ect just a pic
Click to expand...
Click to collapse
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
KilluminatiStyle said:
Super old I know but my kids tablet is doing this now. Did you ever find a fix?
Click to expand...
Click to collapse
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
janekmuric said:
Pro tip: Don't bumb old threads like this. You might not even have similar problems. Instead create a new thread regdaring your issue.
Now, post your tablet info HERE:
Root staus?
Can you boot in recovery? If yes what recovery do you have?
Tablet model
Android version
What happened
What have tried to fix it
Click to expand...
Click to collapse
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
parkourgamer said:
Root Status = ROOTED
I cannot boot into recovery mode (but when i try i get this, look in pic 2&3)
Tablet Type = HKC (NOT HTC) p776a
ANDROID Version I think (98% shure) is 4.1.1 beta JB
What happened = A few years ago 2013 i think a got this tablet then i learned about rooting, roms, and such so i spent the next year or two trying to root the tablet. I finally got it rooted with a chinese root program and all was well (i don't remember the name of the program) then there was a update for su and i pressed the twrp/cwm mode on accident (I think I was talking to someone at the time) and now it does what is shown in the image 1 it is on some boot loop. When I try to access the hboot menu it does what is shown in these images 2&3. Also my tablet has a MicroSD card slot and the battery can not be taken out. the regular bootloop picture is image file 1 that is what it looks like when it does its continuous bootloop and P.S. the tablet turns off and on automatically during the bootloop. To try and fix it i have let it do its bootloop for hours on end turn it on and off tried looking for a compatible rom (to no avail) and let the battery completely die that is about it.
Click to expand...
Click to collapse
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
janekmuric said:
Okay. Just a few more questions.
Does your tablet boot into recovery (picture 1) even if you try to boot normally? (fastboot maybe)
Can you boot into anything else other than recovery? (try different button combinations)
Does ADB recognise your tablet when it's in recovery mode? (if you don't know about this, just post your computer OS and if you have ADB/Fastboot drivers installed on your PC)
If the anwser the the first question is no:
Does ADB recognise the device while it's in the bootloop.
Click to expand...
Click to collapse
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
here is the video
parkourgamer said:
sorry, i forgot to clarify the hboot. it pops up the "words" or whatever then automatically reboots there is no way to select options or keep the device on so i cant use fastboot unless there is a way i dont know of. P.S. the tablet restarts automatically so it is on for like 25 maybe 30 seconds then shuts off then turns back on and repeats till the battery is dead. My thought originally to fix it was to get a rom put it on the sdcard and see if that works but the manufacture does not supply the rom for my model only the p771a. and the only physical buttons are the home, power, the pinhole reset button, the volume and such buttons are virtual on the screen when it is fully on. And picture 1 i dont fully know what that screen symbol is the hboot one is similar but not that but yes it does but to picture 1 nomadder what i do even if i try to get to hboot menu. Sorry if this is a "little" scattered having explaining it. If it would help i can make a video and rar it and upload it here.
Click to expand...
Click to collapse
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
janekmuric said:
1. Download fixcache.bat.zip on your computer. Extract cachefix.bat from the file.
2. Run it. It should say just "Waiting for device..."
3. Now reset your tablet with the reset button and QUICKLY plug it into the computer and wait a few minutes.
Now try to get to that text in picture 1 and tell me what happends.
Also post the text you see on the computer from the file I sent you.
Tell me if
Click to expand...
Click to collapse
this is what happens to the .bat fikle when i open it
parkourgamer said:
this is what happens to the .bat fikle when i open it
Click to expand...
Click to collapse
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
parkourgamer said:
also would there be any way to pop the hood and flip a switch to reset it like on a pc tower?
Click to expand...
Click to collapse
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
janekmuric said:
Umm, you said there is a reset button on the tablet so pressing that would probably reset it.
The error you are getting is because adb is not installed on your PC. Use this simple adb installer to instal adb. When installing just press yes to everything. MAKE SURE THE PHONE IS PLUGGED IN THE COMPUTER WHILE INSTALLING AND THAT IT'S ON!
Now run the file again.
If you want you can add me on Skype: janekmuric
---------- Post added at 13:51 ---------- Previous post was at 13:26 ----------
If you want to know what is happening:
You are in what's called a recovery bootloop. It's when you can't get out of the recovery. What is happening in this case is that Superuser app tried to install it's binaries via recovery. Because some people don't know how to install binaries manually, the app puts a file on the cache partition so the recovery automaticly installs the zip upon booting. Now, this would be good so you don't mess up your device, but the zip file it's trying to install is faulty so it just breaks the device.
My attept at fixing this is to delete the /cache/recovery folder so it doesn't just install the file, and instead boots into a working recovery.
Click to expand...
Click to collapse
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
parkourgamer said:
That would be great but i cant keep my tablet on for more than like 30 seconds before it auto shuts off and it automatically tries to go into recovery when i add power to the device it wont just boot to the OS
Click to expand...
Click to collapse
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
janekmuric said:
30 seconds is more than enough. Especally with an automated script like the one I sent you.
The first thing we have to do to fix your tablet is to establish a working ADB connection. Use the ADB installer i sent you. And look up on how to install Google USB driver for ADB.
Click to expand...
Click to collapse
ok will try