Related
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
Hi guys.
I've recently bought a android tablet,
the brand was MBI and the model was i7
(which is a not known brand ... can't find much info about it).
In my quest of rooting it, I've lost the bundled disc (with Win32 driver). after reading up tons of articles. I've decided to download google's USB driver and edit the .inf, the the tablet's VID & PID info. Somehow I managed to get adb working.
And for rooting, I've tried .apk and none of them work, then I proceed to SuperOneClick and it hung. Lastly I've tried the Easy Rooting Kit by ZoomLord and ta-da, my device is rooted!
Then I attempt to back up the stock rom in case of anything. But Rom Manager kept restarting the device whenever I run 'Back up current ROM'. And when I try to flash the ClockWork Recovery Rom .. the only option was 'Nook Color' & version 3.2.0.1, even Rom Manager reported recovery rom flash successfully, but whenever I try to boot to recovery mode, CWR is not running... and default recovery image doesn't allow me to back up my rom either.
So, in short, I hopes any of you could help me out on following:
1) How do I backup stock rom? or get any recovery rom working?
2) After that, can I just flash to any custom rom? e.g., CM7 Gingerbread ROM? although my device isn't in their supported list?
any help will be appreciated, thanks.
Now I'm trying this fastboot,
somehow when I entered fastboot mode (hold Vol+ & power the device on).
"FastBoot" was showed on center of the screen,
but whenever I issue # fastboot devices
the device will reboot itself ....
any idea? I was trying to flash recovery image via fastboot here
hello
did you manage to root your phone as I too got this tablets thanks
I have a same problem too.. can't use cwm after rooting. Now my mbi i7 tablet can't be used anymore. It just show blank screen after boot up. I can't revert it back to factory setting because the rom is corrupted & the update.zip file is missing. Can anybody upload the update.zip for mbi i7 tablet please.. - sorry 4 my bad english..
Sent from my GT-N8000 using xda app-developers app
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.
Is my device soft bricked?
I flashed PhilZ-cwm6-XXLTA-ATL-5.15.0.tar which worked, then I started up the phone and tried to flash CWM 6.0.4.3 touch using ROMManager, the process was a "success" but after the reboot attempt the phone was unable to boot OS nor is it able to go to Recovery mod. I am still able to enter download mod.
I tried flashing PhilZ-cwm6-XXLTA-ATL-5.15.0.tar again, but it didn't work. I can detect my phone in ADB devices and in Odin3. I am currently searching for a stock ROM for my device.
If anyone has experienced this before and knows the result already, could you tell me whether my device is lost or I can revive it somehow? Thanks in advance.
EDIT: My phone doesn't seem to go into recovery, stuck at manufacturer Logo(Not restarting); but in ADB devices I can see it in recovery mod and can see its contents in adb devices.
Solved: It booted normally after deleting update.img and cache via ADB.
Thread completed as user already founded the solution.
Thread closed
Hey guys!
So, i was trying to install CM13 unofficial version, and wiped the system and internal storage using TWRP recovery. I was supposed to install the rom from a zip file i had placed in the external memory card. What i did, was, i rebooted the phone by mistake, after wiping it from the recovery without installing the ROM and now the phone is caught in a bootloop. I know i am an idiot to do that. I tried removing the battery and reboot it in recovery mode using the key combination with no luck. It just starts the boot loop. I tried using fastboot and adb from pc to push files into the internal memory, but my device is not getting detected on the adb anymore (maybe the usb debugging is disabled now?).
What i guess is stopping TWRP recovery from showing up is the lack of twrp/themes folder in the internal memory since i wiped it. But there might be some other cause that i am unaware of. What do i do now? Any help will be greatly appreciated!
Hey! I'm having the same problem with my yu yureka.. Can anyone help me please!
Kaustubh M said:
Hey guys!
So, i was trying to install CM13 unofficial version, and wiped the system and internal storage using TWRP recovery. I was supposed to install the rom from a zip file i had placed in the external memory card. What i did, was, i rebooted the phone by mistake, after wiping it from the recovery without installing the ROM and now the phone is caught in a bootloop. I know i am an idiot to do that. I tried removing the battery and reboot it in recovery mode using the key combination with no luck. It just starts the boot loop. I tried using fastboot and adb from pc to push files into the internal memory, but my device is not getting detected on the adb anymore (maybe the usb debugging is disabled now?).
What i guess is stopping TWRP recovery from showing up is the lack of twrp/themes folder in the internal memory since i wiped it. But there might be some other cause that i am unaware of. What do i do now? Any help will be greatly appreciated!
Click to expand...
Click to collapse
Hi! I'm having the same problem with this post... Does anyone knows the solution of this problem. I'd be really glad if anyone could help me with this..please!
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
2. You need a PC and a USB cable to connect your phone to the PC.
3. Flashing the factory firmware will wipe all the data present in the internal memory. So, make a backup of that if you can.
4.Install all the necessary Device drivers.
DOWNLOADS -
1. Download the flash tools from here . http://www.mediafire.com/download/87gfz7mdch188an/Flashtools_For_Yu_Yureka.zip
2. Download the factory firmware from Here (cm 12.1) . http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
Steps To Flash Factory Firmware –
1. Extract the flashtools zip in a new folder on the desktop.
2. Extract the factory firmware zip in the same folder and make sure that all of the flashtools files are also present.
3. Now, power off your phone. If you are stuck in a bootloop, then pull out the battery and reinsert it. (Do not switch on the phone.)
4. While pressing the Volume Up key, connect your phone to the PC with the help of a USB cable.
5. You should now see the fastboot logo on your device. If you did, leave the Volume Up key. (If you do not see the logo, retry the process.)
6. Now go to the folder where you extracted the flash tools and factory firmware and run the flash-all.bat by double clicking on it.
7. A command window will open and the flashing procedure will start. (Make sure that your device does not disconnect from your PC during the procedure.)
8. The command window will automatically close once the procedure is completed.
9. Disconnect your device and boot it up by pressing the Power button. (Since this is first boot after flashing the firmware, it may take upto 5 minutes.)
Done you should be back on cm 12.1
Credits – ArnavG (Yuplaygod Forums) and Cyanogen Team.
im also having same problem i have also unknowingly wiped system & now im not able to flash any rom while flashing its rebooting automatically & i am able to enter in to fastboot mode then i have flashed factory firmware then also its not booting stucked on boot loop.
arunbiju969 said:
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
2. You need a PC and a USB cable to connect your phone to the PC.
3. Flashing the factory firmware will wipe all the data present in the internal memory. So, make a backup of that if you can.
4.Install all the necessary Device drivers.
DOWNLOADS -
1. Download the flash tools from here . http://www.mediafire.com/download/87gfz7mdch188an/Flashtools_For_Yu_Yureka.zip
2. Download the factory firmware from Here (cm 12.1) . http://builds.cyngn.com/factory/tomato/cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
Steps To Flash Factory Firmware –
1. Extract the flashtools zip in a new folder on the desktop.
2. Extract the factory firmware zip in the same folder and make sure that all of the flashtools files are also present.
3. Now, power off your phone. If you are stuck in a bootloop, then pull out the battery and reinsert it. (Do not switch on the phone.)
4. While pressing the Volume Up key, connect your phone to the PC with the help of a USB cable.
5. You should now see the fastboot logo on your device. If you did, leave the Volume Up key. (If you do not see the logo, retry the process.)
6. Now go to the folder where you extracted the flash tools and factory firmware and run the flash-all.bat by double clicking on it.
7. A command window will open and the flashing procedure will start. (Make sure that your device does not disconnect from your PC during the procedure.)
8. The command window will automatically close once the procedure is completed.
9. Disconnect your device and boot it up by pressing the Power button. (Since this is first boot after flashing the firmware, it may take upto 5 minutes.)
Done you should be back on cm 12.1
Credits – ArnavG (Yuplaygod Forums) and Cyanogen Team.
Click to expand...
Click to collapse
Bro tried that but nothing........
rss3183 said:
Bro tried that but nothing........
Click to expand...
Click to collapse
Can you be more specific ? Are you facing boot loop too?
anybody please help... facing the same problem and tried the solution as mentioned above but still facing Boot loop. what to do friends. please reply
I suddenly faced bootloop.....then I tried to flash stock rom without root...as a web page suggested me that....it was flashed successfully ...but still I am facing bootloop issue .....can someone pls help me to get out of this mess....pls help me...ASAP !!!
arunbiju969 said:
Hey are you able to boot into fastboot mode? If you can....
Prerequisites –
1. Make sure that you have 70-80% battery on your phone.
Click to expand...
Click to collapse
as its in boot loop battery has come to an end.... now what? having same problem as the topic creator
If you can boot into fastboot try flashing the Twrp from a computer,if you need steps on how to flash Twrp Post here if the flash is successfull boot into recovery and flash A new rom and this should boot your device
arunbiju969 said:
If you can boot into fastboot try flashing the Twrp from a computer,if you need steps on how to flash Twrp Post here if the flash is successfull boot into recovery and flash A new rom and this should boot your device
Click to expand...
Click to collapse
I flashed the factory image via YGDP tool as well as fastboot. But it boots upto a point and then goes in bootloop. Also if i wipe data/cache still it makes no difference. Also unlocked bootloader and twrp also don't load up. Again goes in bootloop.
Yogesh1969 said:
I flashed the factory image via YGDP tool as well as fastboot. But it boots upto a p loopoint and then goes in bootloop. Also if i wipe data/cache still it makes no difference. Also unlocked bootloader and twrp also don't load up. Again goes in bootloop.
Click to expand...
Click to collapse
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Sorry for a late reply...
arunbiju969 said:
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Click to expand...
Click to collapse
The problem got solved bcos it had a battery problem !!!! Battery showed 90-100%, but could not hold up on boot.
A very strange case. Thanks.
Hi, I flashed my Yu Yureka AO5512 Yesterday and entered into recovery mode and selected the wipe userdata option. When it was doing the process after 20min the process stopped all together and My phone does not start at all now. If i press any button there is no response at all. Looks like phones OS and everything is wiped out. How do i go about from here?
Same problem , Stuck in BootLoop
arunbiju969 said:
were you trying to flash the twrp for the first time?? Was your yureka plus on stock kitkat??
Click to expand...
Click to collapse
Bro , my Yureka was on Stock Lollipop (5.1) and i flashed Twrp 2.8x.x on it and now it''s Stuck in bootloop , i can't turn of the phone nor it starts , what should i do , any help appreciated
Thanks
YuganshT7 said:
Bro , my Yureka was on Stock Lollipop (5.1) and i flashed Twrp 2.8x.x on it and now it''s Stuck in bootloop , i can't turn of the phone nor it starts , what should i do , any help appreciated
Thanks
Click to expand...
Click to collapse
Sorry to hear that anyway,
By stock lolipop you mean you had the yureka plus with Volte From factory right!!...if so the twrp might have been for the yureka plus with the cm bootloader which got replaced in the new Devcice
I am facing the same problem and in my case I dont think its an battery issue...I was happily using the CM 13.0 Snapshot Rom since a long time...but today morning when I did a soft reset by going into the settings in my yureka...the phone has gone in bootloop...and nothing is working...using fastboot I even flashed the twrp again and also flashed the CM 12.0 Stock firmware..but nothing is working...after the YU logo it restarts....please help...
I am also facing problem maybe worst
I dont know what wrong I am doing but I am getting "FAILED (remote: unknown command)".
Few info:
1. I get my device ID when I do "fastboot devices" but nothing on fastboot -i 0x1ebf oem device-info".
2. Also for my YU5510A fastboot screen doesnt say' "fastboot" it says "Information do not unplug the cable - Secure Phone".
3. I have red light on, phones keeps rebooting 4-5 times than red light goes off and charging stops.
Aditi Apte said:
I dont know what wrong I am doing but I am getting "FAILED (remote: unknown command)".
Few info:
1. I get my device ID when I do "fastboot devices" but nothing on fastboot -i 0x1ebf oem device-info".
2. Also for my YU5510A fastboot screen doesnt say' "fastboot" it says "Information do not unplug the cable - Secure Phone".
3. I have red light on, phones keeps rebooting 4-5 times than red light goes off and charging stops.
Click to expand...
Click to collapse
Ignore that and use other fastboot commands and go ahead, as your device is being detected in fastboot mode.
FAILED (remote: unknown command)
Yogesh1969 said:
Ignore that and use other fastboot commands and go ahead, as your device is being detected in fastboot mode.
Click to expand...
Click to collapse
But when I am executing other fastboot commands it halts the process between with error "FAILED (remote: unknown command)".
I have read about this error and people suggested that I need to get into "Download mode" not "fastboot/bootload". To get into "download" mode I tried pressing "VoulumeDown+Power+Home", but nothing happened, it simply restarted the phone.
Please advise.
-Aditi