I am a beginner at this so please excuse me.
I successfully rooted my phone, installed clockwork, super user was working, could connect like a dream with usb to the phone. Flashed stuff using fastboot in command line - all was good.
When I say successfully it did take a long time, the phone didnt work for a while but I flashed clockwork on then flashed the rom for my phone from here http://forum.xda-developers.com/archive/index.php/t-1063664.html
I used this one:
Android 2.3.3/GRI40/KB1 Radio/KA3 Bootloader (http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip)
Works on: I9020T, I9023
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Which was great - sorted the phone a treat - I had the super user working - I installed the clockwork rom app - worked a treat - even did a backup (I think)
Then the phone tried to update to 2.3.4 which failed - right now I should of check the forums but thought I know I'll just flash the update from the above page - which failed - not to be defeated I tried harder using different roms through clockwork recovery or clockwork rom mod until sucess 2.3.4 GRJ22 build.
Then I find the super user app doesnt work or the clockwork rom - no problem boot into clockwork recovery - uh oh thats gone as well though i can get to android recovery.
I'll just flash clockwork recovery on but I cant as I've no access with adb or fastboot the phone is not connecting to the pc in fastboot mode with the android logo and phone details.
When I'm trying to use USB connection on the phone normally the USB man goes orange then back to green - and the phone prepares the USB storage again.
I can use a app to get files on to the sd card for use with android recovery so i try to reflash the 2.3.3 rom above that worked but I get the status 7 error with a long number 1297306095
I try the update again and this is where i realise that the update ROM i put on was the wrong one.
I flashed this: Android 2.3.3 (Build GRI54/KB3 Radio/KA3 Bootloader) (whole rom)
I should of flashed this Android 2.3.3 (Build GRI40/KB1 Radio/KA3 Bootloader) (smaller update)
I can flash the correct update above but it doesnt change anything.
I have spent a few days now trawling the forum with little success and having got all the correct drivers on the pc and had it connecting fine I am assuming it is a phone issue now
the base band details have changed from XXKB1 to XXKD1 and the build from GRI40 to GRJ22
I am at my wits end here and before I put a hammer to my phone and send it back as an insurance job I'd like to mend my stupid mistakes.
Thanks
Acne
it doesnt matter if you flashed the whole rom. (provided you didnt use odin)
first thing, try to format sd card through the phone,
then enable usb debugging and try using adb n fastboot.
also, try to flash a newer recovery.img ( be careful no to use one not meant for ur phone e.g ns4g...)
post ur results.
good luck
can't find an option from within the phone to format the SD card - found an app on the store that is called "format sd" which did something and allowed me to connect to the USB once but it was very flaky and took a few attempts at the "turn on usb" screen to get it to connect. I'm not sure that it wasnt just deleting the data from the sd rather than formatting as it took maybe 10 seconds first time and now its done straight away if I try again.
Edit - i've used the stock erase usb command within the phone and the USB connection within the phone seems to becoming more stable - I can read and write data to it from the pc but it still struggles to connect first time.
No change with command line commands abd or fastboot neither are connecting.
I've come to the conclusion that maybe I need to flash a newer recovery image (ROM?) myself but where do I find one? And how do i check that it really is the correct one for my phone - which of the details are important - should i use the original stock details? I'm confused, remembering all I can use is the "Android system recovery <3e>" that only gives me the option of reboot, apply update from sd card, wipe data/factory reset, & wipe cache partition.
I flashed the wrong ROM with the clockwork rom app from within the phone I dont know what odin is.
Thanks for the pointer anymore ideas or direction appreciated.
Acne
Try to wipe from the stock recovery and then install this
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip
It is the full 2.3.3. It will return your phone to complete stock 2.3.3
P.s sorry i am not being able to help more. I am myself in a far bigger trouble
I tried that rom but got the status7 error. That one worked before under clockwork but won't reflash now. I can do a factory reset under stock but will that make a difference? I thought all that did was reset user data not the system data. I think l need to wait for a new stock Tom to be issued.
Acne
Tried the reset phone from within the phone and reset using stock recovery, still cant flash the old 2.3.3 rom above getting the status 7 error:
assert failed ! less_than _int(1297306095. getprop(ro.build.date.utc"))
so the usb works fine from within the phone when the phone is running normally, when I connect the phone in fastboot mode it shows as an Android ADB interface on the "safely remove hardware" window but i cant use any command prompt instructions on the phone - using fastboot devices to show connected devices I get no reponse.
Any ideas?
Any pointers to a later rom that will correct my problems?
Thanks
Acne
After a bit of experimenting I find that when the phone is switched on normally I can use the ADB devices command to return the ID of the phone. The fastboot devices command still returns a blank.
Is this normal?
Does this mean I could flash the clockwork recovery image onto the phone? or can all that malarkey only be done in fastboot mode?
thanks
Acne
You need the fastboot devices command to return your phone info then you can fastboot flash recovery in order to try flashing a recovery that will allow you to flash the rom you are getting a failed message from. The stock recovery can only flash official updates put out by Google iirc.
I am thinking you are having driver issues on the PC you are using. Try another PC with fresh drivers or uninstall and reinstall the drivers on the one you have been using.
sent from the nexus of the 4g universe
I've read up on the driver problems, I tried the phone on two different pcs using two different methods on each to install the correct drivers. none work. The phone used to connect fine which is how i rooted the phone. I'm using the same pc, same supplied cable and can see the ADB mounted in the "safely remove hardware" window
The adb command works when the phone is switched on normally, but not fastboot command.
When in fastboot mode neither works. Looking in device manager the android adb interface is listed fine under android phone.
I'm pretty sure its not the drivers.
Doesn't the above prove that the pc connects fine but the phone is broken in fastboot mode?
You could still flash the latest 2.3.4 full ROM with ODIN. The Phone will be restored completely and then you can root it again.
Thats great Odin looks like it will be the way forward, just so I dont make another noob error could someone point me in the right direction for the correct version of odin and a guide on how to use it. I have looked around the forum but am struggling to find the relevant thread
I have tried the usb/2 button and it enters download, the version od odin that i found (1.81) does see the phone but I think that version is for the 9020 only I have the GT-i9023 so dont want to use the wrong programme/rom
Thanks
Acne
Ok took a chance and flashed the phone with odin - great it worked reset all the fastboot mode values back to their original ones when i got the phone. (seems I chose the correct rom) the only difference is that the Carrier info is now EUR not VDF as it was when I first got the phone.
Applied the auto update to 2.3.4
Tried at every step but I still have no fastboot or ADB access the phone just doesnt connect. Tried different leads, tried different usb ports - nothing.
I'm stumped now unless there are any advanced settings in odin I should try.
Acne
The
Discovered after the auto update to 2.3.4 that the USB connection from within the phone was "broken" again, To sort this i did a format cache and reset phone from the stock recovery which sorted the usb connection. so thats that one solved then.
tried again to connect via command prompt, unistalled drivers - reinstalled drivers - no change still no devices detetcted.
Any good ideas?
Solved
using the usbdeview mentioned here I uninstalled all the usb drivers on my pc that looked like they could be anything remotely connected to the nexus and samsung.
I ran and updated/download pretty much everything i could through SDK
Then I did everything I read in this thread
Up till then I had been using the fastboot command found and downloaded through this thread
That continued not to work but when i tried the fastboot in the android-sdk/tools folder I finally got fastboot access.
Solved Solved Solved
to get my phone unlocked and updated I did an odin restore to 2.3.3 let it auto update to 2.3.4 copied the su(superuser zip) to the sd card. flashed clockwork recovery and then installed the su.zip with clockwork. after that I installed the rom manager from the android shop and Inow have the phone just how i want it.
To all those that have helped with their ideas here many many thanks.
Acne
Related
Hi there I have a Nexus S with 4.04 on it, so the other day I followed the instruction online and tried to root the phone, I have phone driver installed, and able to unlock my bootloader, the LOCK STATE is UNLOCKED. and I was able to flash Clockworkmod recovery v5.0.2.0.
But after this step, and I tried to reboot, my phone just stuck at the google logo with the unlock sign at the bottom, and wouldn't do anything afterward. (seems like a root loop?)
I tried pulling off the batt a few times but no good. I am still able to lock and unlock bootloader through cmd.(just like in normal state)
I tried to install factory img as shown in the thread http://forum.xda-developers.com/showthread.php?t=1572307. but when I type in the first line "adb reboot bootloader", it says adb devices not found.
so, any idea on how I can restore back to the factory img?
bootloader version i9020xxkl1
model GT-i9020T or if any more info is needed I will be here.....>.<
Did you correctly installed the recovery?
Hi.
First at all let me tell you that I'm not an expert. So, I understand that you should double check this.
I think that you should try to:
- If you have successfully installed the ClockworkMod recovery, you should turn on the device on recovery mode. Vol up + on pushbutton to go inside bootloader. Going down with Vol down, go to recovery and select with on pushbutton.
- Download the correct superuser app for your version. I would double check the md5sum of the file that you have downloaded on your computer.
- Mounting the usb storage of the device on your computer, add the superuser app on /sdcard.
- Umount the usb storage.
- Flash the superuser app, installing from /sdcard from your recovery menu.
- Download a custom kernel on your computer, once that you are unlocked. I'm using CyberGR, and I'm happy with it. You can see all the intallation instructions in the Nexus S development part.
- I that works, I would try to install the kernel in a clear way. For installing the CyberGR ROM, you need to wipe everything and format all. After that, you mount the device on the computer, and try the installation.
Then, if everything is ok, the device will turn on.
Again, I'm not an expert, and I don't know how you can be in contact with the developers that are posting in the developers area. I'm not responsible if your device doesn't works or get bricked.
However, I understand that all that I have described, should not put your device in a worst situation.
And is it doesn't turn on, if it doesn't do anything, then, you can use the linux tooll for bicked devices explained on the developers area.
So basically I rooted my LG p500h and installed a ROM through ROM manager, the thing is that when I rebooted the device I got stuck at the analog to the Android logo that shows up after the LG logo. I flashed an stock ROM through KDZ update software but after the program did it's thing, I did hard reset the phone and got the same problem: won't boot up and forever stuck at the android logo. I can get to emergency mode tho and when usb connected will show the battery charging up. I have searched solutions and I haven't reached one yet so everyone told me to post here and ask for some help! I hope it's not the end of my device Any help is sincerly appreciated!
Secretagogo said:
So basically I rooted my LG p500h and installed a ROM through ROM manager, the thing is that when I rebooted the device I got stuck at the analog to the Android logo that shows up after the LG logo. I flashed an stock ROM through KDZ update software but after the program did it's thing, I did hard reset the phone and got the same problem: won't boot up and forever stuck at the android logo. I can get to emergency mode tho and when usb connected will show the battery charging up. I have searched solutions and I haven't reached one yet so everyone told me to post here and ask for some help! I hope it's not the end of my device Any help is sincerly appreciated!
Click to expand...
Click to collapse
Much as I hate to say it, ROM Manager is not friendly to our devices. Secondly, stay away from KDZ too. But don't panic. You do have options. You will need to use either ADB and dd commands, or fastboot and fastboot mode. Since you can't boot, most likely the ADB way won't work ATM. Both methods require either the ADB binaries or the Android SDK. An alternate method would be Android Flash Recovery. There is a link in my signature. There are complete instructions in the download. On thing, put the device in fastboot mode before connecting it to the PC.
Enter into emergency mode, BACK+VOL UP+POWER
then follow this guide to flash recovery: http://forum.xda-developers.com/showpost.php?p=15217609&postcount=3
After that enter into recovery, HOME+VOL DOWN+POWER
then wipe data/factory reset, wipe dalvik cache, wipe cache, format system then flash a rom of your choice like oxygen, cm9 present in development section.
Then reboot
shinobisoft said:
Much as I hate to say it, ROM Manager is not friendly to our devices. Secondly, stay away from KDZ too. But don't panic. You do have options. You will need to use either ADB and dd commands, or fastboot and fastboot mode. Since you can't boot, most likely the ADB way won't work ATM. Both methods require either the ADB binaries or the Android SDK. An alternate method would be Android Flash Recovery. There is a link in my signature. There are complete instructions in the download. On thing, put the device in fastboot mode before connecting it to the PC.
Click to expand...
Click to collapse
Odd enough, I plugged in the device to the computer after the USB drivers got installed (following all the instructions given by the files provided), I went to the bathroom and left the cell phone unattended, just to find it boot up! weird. Anyways your advice was very helpful and very clear! Now I will figure out how to get my old ROM for my country. Thanks again!
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?
I have problems with my pantech discover magnus P9090, the problem is that the phone is completely bricked and dead. When i turned on the phone, it simply just shows BLACK SCREEN ( No Logo and nothing else). My assumption is that there is no OS inside or something causes it to be bricked. I have done almost everything by using Android Recovery (Not custom recovery) to do factory reset and wipe cache. I rebooted it and it doesn't work either. So i found a solution which is by using apply update from ADB. I understand the process but the only problem is
The device is not detected by ADB when i type "adb devices" it could be two problems:
a. No drivers for this phone installed (While i try to update driver, it fails)
b. USB Debugging off (Since phone can't get into OS, so im confused how to turn it on via other ways)
I got the Custom rom and CWM recovery image but how can i install the recovery and ROM if ADB isn't detecting the phone. I can't even use sideload command.
My plan to fix this is by installing CWM with the command "fastboot flash recovery [filename]" and then using CWM to push the file ROM into phone and install zip in SD card. However, it links back that i need the phone to be detected first. Anyone can help me? Thank you so much. Im so badly want to revive this phone. :good:
There's no other way until pantech usa release pdl file for restore discover..
Sent from my ZTE N986 using XDA-Developers mobile app
Hello, first post on XDA forums.
In one sentence, my goal is to back up data from a tablet that doesn't boot beyond the Samsung logo.
Details:
- tablet: Samsung Galaxy Tab 2 7.0", model GT-P3113
- problem: when you turn it on, it boots to the point of showing the Samsung logo and is stuck on it
For the past 2 days now, I've been trying to figure out how to back up data from this tablet so that it can be put on a new tablet.
During these 2 days, I educated myself on Android and especially how to use Odin to install new firmware and I've been reading about TWRP. I learned about recovery mode and download mode.
I was able to use Odin to load a ROM image for version 4.2.2 and according to Odin the process went through without issues. However, that didn't fix the boot problem, it's still the same.
I even wiped the cache partition in recovery mode but still the same problem.
I was very hopeful today that I would be able to use ADB with the "pull" command to save the data to a computer. Unfortunately, after installing ADB on my laptop running Ubuntu, it doesn't see any devices connected. My understanding is that with Linux there is no need to install a driver unlike on a Windows PC.
Current situation as I type this message:
- stock tablet, not rooted, default recovery system on it (Android system recovery <3e>)
- tablet in recovery mode
- tablet connected to computer via USB cable
- ADB installed on Linux computer
- the command "adb devices" returns no devices found
Question to you guys: if the tablet is in recovery mode, shouldn't ADB see it on the Linux-based computer?
Please advise.
Thank you in advance for your help. :fingers-crossed:
mjitkop said:
Hello, first post on XDA forums.
In one sentence, my goal is to back up data from a tablet that doesn't boot beyond the Samsung logo.
Details:
- tablet: Samsung Galaxy Tab 2 7.0", model GT-P3113
- problem: when you turn it on, it boots to the point of showing the Samsung logo and is stuck on it
For the past 2 days now, I've been trying to figure out how to back up data from this tablet so that it can be put on a new tablet.
During these 2 days, I educated myself on Android and especially how to use Odin to install new firmware and I've been reading about TWRP. I learned about recovery mode and download mode.
I was able to use Odin to load a ROM image for version 4.2.2 and according to Odin the process went through without issues. However, that didn't fix the boot problem, it's still the same.
I even wiped the cache partition in recovery mode but still the same problem.
I was very hopeful today that I would be able to use ADB with the "pull" command to save the data to a computer. Unfortunately, after installing ADB on my laptop running Ubuntu, it doesn't see any devices connected. My understanding is that with Linux there is no need to install a driver unlike on a Windows PC.
Current situation as I type this message:
- stock tablet, not rooted, default recovery system on it (Android system recovery <3e>)
- tablet in recovery mode
- tablet connected to computer via USB cable
- ADB installed on Linux computer
- the command "adb devices" returns no devices found
Question to you guys: if the tablet is in recovery mode, shouldn't ADB see it on the Linux-based computer?
Please advise.
Thank you in advance for your help. :fingers-crossed:
Click to expand...
Click to collapse
It seems u got stuck in the bootloop, try to wipe data/cache/dalvik ur device and I think it would solve ur problem
root the tab, install custom recovery twrp and a nice marshmallow custom rom. then you have a new device.
why backup data from a non booting system?? for me it makes no sense.
mjitkop said:
In one sentence, my goal is to back up data from a tablet that doesn't boot beyond the Samsung logo.
Details:
- tablet: Samsung Galaxy Tab 2 7.0", model GT-P3113
- problem: when you turn it on, it boots to the point of showing the Samsung logo and is stuck on it
For the past 2 days now, I've been trying to figure out how to back up data from this tablet so that it can be put on a new tablet.
During these 2 days, I educated myself on Android and especially how to use Odin to install new firmware and I've been reading about TWRP. I learned about recovery mode and download mode.
I was able to use Odin to load a ROM image for version 4.2.2 and according to Odin the process went through without issues. However, that didn't fix the boot problem, it's still the same.
I even wiped the cache partition in recovery mode but still the same problem.
I was very hopeful today that I would be able to use ADB with the "pull" command to save the data to a computer. Unfortunately, after installing ADB on my laptop running Ubuntu, it doesn't see any devices connected. My understanding is that with Linux there is no need to install a driver unlike on a Windows PC.
Thank you in advance for your help. :fingers-crossed:
Click to expand...
Click to collapse
considering you never rooted,
and you were on stock 4.0.4 or 4.2.2?
whichever version you were on, you're supposed to use the same firmware build which you were using before.
different firmware flashed on another Build's data results in bootloops as well.
solution: you should flash a custom recovery first instead of a firmware. that will not erase the data.
then you switch to recovery, make a backup of the data partition.
save it on your ext card.
wipe your system,data, factory reset.
flash the official firmware you were using before.
let it boot.
flash custom recovery again.
restore data and check.
if it still goes into a bootloop,
try entering safe mode.
you can get an app that can restore selective data from nandroid backup. (forgot the name but it was on play store) or you can extract from the backup the data you need.
there is a detailed guide link just below here in my signature. you can give it a read, when you feel like stuck somewhere.