Bricked I/O tab 10.1? - Galaxy Tab 10.1 General

[SOLVED] Okay so I got my i/o tab back up and working. See this post http://forum.xda-developers.com/showpost.php?p=14586131&postcount=2.
1. I downloaded those 2 things.
2. I booted into odin mode by powering off the device and holding the power and the left volume (volume down) until it brings me to a usb and a triangle sign with an android figure.
3. Press Right volume (volume up) to select the right icon on the screen.
4. Plugin the tab to your computer and load the odin3 v1.85 application.
5. Press PDA and find the PDA_SIGNED_P7105.tar.md5 file
6. Click start and let it reboot and it should be fixed! (well that's what fixed it for me)
So I tried installing the starburst rom on my i/o tab that I won (from phandroid!), anyways I was on an unlocked 3.1 rom that was rooted. So I installed rom manager from the market to get cwm on it. After that I backed up my current rom, and then I flashed the starburst rom.
After the rom finished flashing it rebooted and is now stuck in a bootloop of continually showing the samsung galaxy tab 10.1 splash screen.
I can't get back into cwm at all. I've tried getting it back with odin and with nvflash. Also fastboot isn't working for me (says waiting for devices both on my windows and linux machine). I've tried flashing both stock recovery and cwm via odin and via nvflash but nothing is working.
I'm not really sure where to go from here. I've spent the last 5 hours or so on xda and google. Any help would be appreciated.
The first attached files shows what happens when I select the USB image, the second shows what I get when I hold down the power and down volume, and the third is me flashing cwm through odin, but after flashing it, I still can't get into cwm.

I'm not an expert, but you may want to check the file you are trying to flash as it may be corrupt. Maybe try redownloading and flashing with odin. If that does not work you may need to reflash your firmware, I think there is instructions in the dev form on where to download. Also check if the IO edition is different model from the retail WIFI version.
Hopefully this is helpful,if not I'm sure someone else will chime in.

I checked the md5 of it and it matched. How would I reflash with odin? All I can see that I can flash with odin is the recovery. I don't know how to flash anything on my tab in it's current state. I can't get cwm back, and all I get is fastboot usb mode and odin. Fastboot isn't working and odin says it flashes the cwm recovery correctly and everything, but then it's not there.
Thanks for your input, any input is greatly appreciated. Was hoping to get my tab updated to a touchwiz rom, now I can't even use it.

I had same problem happen with mine out of the blue and it's stock I/O.

Maybe the thing i'm flashing in odin isn't for the I/O tab?
kbutlermd said:
I had same problem happen with mine out of the blue and it's stock I/O.
Click to expand...
Click to collapse
Did you fix it? I had this happen once before but I forget how I was able to get fastboot to work to issue a fastboot -w command.

Okay, so I think I made some progress. I was able to get fastboot working on a fresh computer that never had adb, fastboot, or the android sdk installed. I only have fastboot working on it and not adb. :\
So I tried fastboot flash system stockrom.zip but when rebooting it just shows the
splash screen. (I waited like 10mins). I now do have fastboot working so now what should I do?

mjm128 said:
Okay, so I think I made some progress. I was able to get fastboot working on a fresh computer that never had adb, fastboot, or the android sdk installed. I only have fastboot working on it and not adb. :\
So I tried fastboot flash system stockrom.zip but when rebooting it just shows the
splash screen. (I waited like 10mins). I now do have fastboot working so now what should I do?
Click to expand...
Click to collapse
which stock rom are you using? are you using the OTA 3.1 that is in the dev thread?
try that and lemme know what happens
also, if you can get into fastboot, you can fastboot recovery, ie get back into CWM and load a backup

used2hvatreo said:
which stock rom are you using? are you using the OTA 3.1 that is in the dev thread?
try that and lemme know what happens
also, if you can get into fastboot, you can fastboot recovery, ie get back into CWM and load a backup
Click to expand...
Click to collapse
I think maybe my partition table is effed up? I'm not sure.
I tried fastboot and flashing the backup that I had on my computer (fastboot flash system system.img ; fastboot flash data data.img ; etc), but it just hangs at the samsung galaxy tab splash logo.
I'm using the ota that comes in the files for dummies in the dev forum.

thank you SO MUCH ... I was stuck for hours until I found your thread

but i have p 7500
not recognised by odin
tab is in """'NVIDIA USB Boot-recovery driver for Mobile devices""""""
shown in device manager
any solution to revive it
??????????

Sheeda Talli said:
but i have p 7500
not recognised by odin
tab is in """'NVIDIA USB Boot-recovery driver for Mobile devices""""""
shown in device manager
any solution to revive it
??????????
Click to expand...
Click to collapse
you are not in download or recovery mode. turn your tab all the way off, and then use the key-combo to get into the menu where you choose recovery or download mode.
then odin will see it

Jtag will available soon for 10.1

which key combination ??????????
there is nothing shown on my tab
no light
no charging sign
blank black lcd while in """'NVIDIA USB Boot-recovery driver for Mobile devices"""""" mode
in device manager
so good to hear that mine is not bricked

So annoying coming back to this thread because my tab decided to randomly boot loop again. >.>

mjm128 said:
So annoying coming back to this thread because my tab decided to randomly boot loop again. >.>
Click to expand...
Click to collapse
fastboot -w ..
my suspect is data / cache becomes corrupt or gets corrupted easily .. seems like it happens on a few tabs .. I have 3 and only 1 keeps giving me problems ..

gunzo71 said:
fastboot -w ..
my suspect is data / cache becomes corrupt or gets corrupted easily .. seems like it happens on a few tabs .. I have 3 and only 1 keeps giving me problems ..
Click to expand...
Click to collapse
Simply doing fastboot -w has never worked for me. It would just bootloop. Only way i've been able to restore it is through the steps I listed in this thread.

Related

[Q] ClockworkMod Recovery 5.0.0.1 flashed from ROM manager failed. trying again

I just got the new CWM recovery update through Rom Manager today, and it said it was successfully flashed, but the phone only hangs on the HTC logo when goingto recovery. I can still do fastboot and boot to Android tho, so I'm now gonna try to figure out how to get my recovery back before something bad happes xD
anyone have advice or know where I can download a standalone copy of CWM 5.0.0.1 for G2?
Wish me luck I'll keep updating as things progress
okipokey, solved my own issue. Just had to reflash back to an older recovery and try again a couple times before it stuck.
Time to test out the new recovery!
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Same here just reinstalled the new version and it worked second time round
must be a bug they havn't quite worked out. Next time I'll do a fastboot flash instead for a low build number.
First time I flashed I tried it from a battery pull through HBOOT and it still hung. Reflash to 3.5 and then back to 5.0 fixed it like you guys
epolaris said:
I decided to flash the upgrade as well. The flash went perfectly. However, I couldn't boot into recovery while within Android. I had to power off and boot into the bootloader and then select recovery... Whenever I tried to reboot to recovery via the Android UI, it restarted and hung at the boot splash screen.. It didn't even work if you selected the option from the ROM Manager itself... I rolled back to previous version as well and its working again. It may be a bug... Early adopters nightmare....
Click to expand...
Click to collapse
try just reflashing version 5 I had the same problem,but rebooted the phone reflashed version 5 from the rom manager and now is all good
I just sent the dev a comment about it on his Google+
maybe he'll have a fix out soon
Nice one, seems a "double flash" fixes it have just tested 3 or 4 times,seems to be working
yessir, seems to me that if it's a bug its really minor. I can see this being a problem if someone accidentally screws up something on their phone right after flashing the recovery, but not very likely and they'd still be able to reflash through fastboot
Seemed to flash the new version ok. But then, when trying to boot into recovery for the first time, the phone hung on the HTC logo boot splash. Pulled battery, and booted into recovery ok after that.
that's interesting that some of you didn't hang after the battery pull while mine did. Maybe it depends which version we're upgrading from?
stuck at htc
hey i also had this problem and i can't get my g2 to boot up at all. It hangs at the htc screen. I don't know how to fix this issue as i was trying to restore a backup from recovery right after the update. i can't get into recovery or anything else...all i get is the htc screen. Any ideas how I can fix this?
Luis
Any sign of a changelog?
I have no idea how to get to a changelog...can you tell me how?
biglou421 said:
I have no idea how to get to a changelog...can you tell me how?
Click to expand...
Click to collapse
found this
-From Mr.Dutta via G+
I've just finished releasing updates to a bunch of devices to ClockworkMod Recovery 5.
Major changes:
Backups now use tar over yaffs for everything except mtd partitions. Backups got way faster.
Backups now preserve the filesystem type at time of backup. Restores will restore the appropriate filesystem type at restore.
Please update to ROM Manager 4.4.0.3 or higher and try out the new recovery!
Troubleshooting:
Flashing issues: If a recovery does not flash properly, enable erase recovery in settings and try flashing it again. Recovery flashing can be finicky at times.
Bugs: Report them to me! You can always revert back to the older recovery too from within ROM Manager!
So far no issues here while playing around.
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
biglou421 said:
my issue is i can't get back to android at all now. i went into rom manager to restore a backup and was told there was an update, then it reflashed the recovery. When i tried to restore my backup it froze and i have not been able to get past the htc screen at all.
Click to expand...
Click to collapse
can you get into the HBOOT?
pull the battery, put it back in, hold the volume down button and then hit the power button. you should come to a white screen with some options
In the case you want to update your recovery using fastboot method, heres what you'll need:
CWM 5.0.0.1 for G2 (Vision)
HTC Sync drivers
ADB fastboot from Android SDK
Make sure your phone is all the way off by pulling the battery. Get into the HBOOT by holding down the volume down button and then hitting the power. use the volume keys to navigate and the power button to select. Choose "FASTBOOT"
Rename the recovery that you downloaded from CWM to "recovery.img" and put it in your ADB and Fastboot folder
plug your phone into your computer and pull up a command line for your adb/tools/ or adb/platform-tools/ folder where you should have ADB and Fastboot.
under the command line type in:
fastboot devices
<list of devices>
If you do not see your device make sure the cable is plugged in and your drivers are installed. if still nothing try a different cable til you get it to be recognized by the computer.
Once it's recognized do:
fastboot flash recovery recovery.img
when its done:
reboot
I flashed through ROM manager. On suggestion, I checked the box for "erase recovery - recovery will be erased prior to flashing". On first reboot to recovery it sticks at HTC screen. Pulling battery and vol. up+power then entering recovery the 2nd time works just fine.
Hope this helps.

[Q] apx flash utility usb boot recovery driver

acer a500 usb boot recovery driver in the window 7 device manager disappear when entering download mode using blackthund3r a500 apx flash utility have tried about 10 times with no luck
shenny585 said:
acer a500 usb boot recovery driver in the window 7 device manager disappear when entering download mode using blackthund3r a500 apx flash utility have tried about 10 times with no luck
Click to expand...
Click to collapse
Follow along with this step by step - "Pictorial" "How to Use the apxFlash Tool"
how far do you get and what doesnt 'work'?
Did you install the right drivers?
apx flash utility
I got as far as are you ready to flash I press yes when downloading starts the driver disappears. I tried the manual method and auto mathod. I used the guide an followed it
a500 flash utility
yes it is the right driver. download it from the acer a500 support site
You should see a cmd prompt come up and load a few lines up then flash off the screen. At that point your tab should vibrate and say sumthin like "Entering Acer Download mode" with the acer logo in the middle.
I don't remember if mine disappeared or not, I know I kept an eye out for it the first time I flashed the BL. I read this after I flashed to v4, I would have checked had I read it earlier...sorry
As long as the little usb icon appears at the bottom of the screen it should be OK. Make sure you don't have any other usb devices attached... Right click on the usb icon and it should say apx device...
I always use manual method to update bootloader and recovery as I can't seem to get blackthund3r's tool to work....
You do need to be in APX mode though... Supposed to be tricky manually but I just stick a LED leg into the reset hole, press power 3 secs then a sec later release the reset button. Works every time...
shenny585 said:
I got as far as are you ready to flash I press yes when downloading starts the driver disappears. I tried the manual method and auto mathod. I used the guide an followed it
Click to expand...
Click to collapse
ok we wont be too concerned with the driver disappearing just yet...
you get the are you ready to flash window and click yes
then the you have 8 seconds to cancel window pops up
and then the "flashing ....entering download mode bootloader pops up
so what do you see after clicking yes to the are you ready window
also what rom are you on now and which package are you trying to flash??
apx flash utility
I see entering dowload mode bootlander- flashing boot loader-flashing kernel-flashing recovery-exiting bootloader
package-V3 bootloader
rom- ICS AV041 a500_1.031.00_ww_Gen1
shenny585 said:
I see entering dowload mode bootlander- flashing boot loader-flashing kernel-flashing recovery-exiting bootloader
package-V3 bootloader
rom- ICS AV041 a500_1.031.00_ww_Gen1
Click to expand...
Click to collapse
yep - nothing wrong there
ok lets take another step back
- apart from the driver disappearing do you have any other problems????
cos to me it doesnt seem that you do????
- so what happens on your tab that u dont or do see in the guide??
apx flash utility
Reading the guide again I notice the tab does not vibrate but the screen say
"Entering Download Mode"
shenny585 said:
Reading the guide again I notice the tab does not vibrate but the screen say
"Entering Download Mode"
Click to expand...
Click to collapse
Lol, m8 U ain't making this easy for me r u??.
Put it this way then,
Do u have a problem, cos I'm not hearing one . Does the tool fail to flash woteva it is u r trying to flash, does it get stuck and go no further, does yr tab not boot or something ...is the guide wrong,...I dunno???
So there aren't a lot of steps left to go - download mode u got OK, flashing u got OK, assume got "Done" window
So, either u still on v3 and u wanted v4 OR..............
The tool does not flash anything, another thing I notice in the guide the power light stays on, by the way I noticed at bottom of the tool it says apx decvice is connected.
shenny585 said:
The tool does not flash anything, another thing I notice in the guide the power light stays on, by the way I noticed at bottom of the tool it says apx decvice is connected.
Click to expand...
Click to collapse
OK now we're cooking...... everything you've said you've done and seen is all OK ant there should be no reason why the flash hasn't worked....
U posted this earlier "package-V3 bootloader rom- ICS AV041 a500_1.031.00_ww_Gen1"
Is this what u wish to flash to?
You've chosen not to flash custom recovery, is that correct..?
There is an updated version But its not mandatory you have it. you will be alright on v3
-A500-V4-CWM1.7.a500apx or
-A500-V4-CWM1.7.2.a500apx with latest CWM-1.7.2
Download Acer recovery installer if u dont already have it.
open it up and tell me what BL & Recovery version it says u have
Silly question maybe, but are rooted??
apx flash utility
Yes I have not chosen to flash custom recovery
Yes I am rooted
Acer Recovery Installer:
BL-0.03.12-ICS
Recovery Version-CWM rev1.7 by thor2002ro(for ICS Bootlloader)
The problem here is when a boot into recevery. I get (recovery verified failed ) after I updated to new ICS OTA that when the error started.
Used the Acer Recovery Installer and Power Bottom-Vol-Down same results.
shenny585 said:
Yes I have not chosen to flash custom recovery
Yes I am rooted
Acer Recovery Installer:
BL-0.03.12-ICS
Recovery Version-CWM rev1.7 by thor2002ro(for ICS Bootlloader)
The problem here is when a boot into recevery. I get (recovery verified failed ) after I updated to new ICS OTA that when the error started.
Used the Acer Recovery Installer and Power Bottom-Vol-Down same results.
Click to expand...
Click to collapse
M8, that took along time to get to the real problem and is what u should have posted right from the beginning!!!!!
The OTA has wiped yr cwm recovery and root - Yes that's just what they do
You've re-rooted - OK fine
Problem - recovery verified failed after OTA update
U have tried to fix using apxFlash - but chose not to flash a custom recovery (CWM)
Your recovery is borked so u have to put a new one on there, the best way to
go about doing this is to:
Download the V3 AND CWM Recovery package and apxFlash that.....Done!!
your need to flash the WHOLE PACKAGE b/c ARI reports yr BL as plain old stock
You cannot replace the failed recovery with CWM with the plain old stock BL!!
You have to flash the patched BL as well, so again
You must flash the whole pckg just like in the guide OK
if later u want the stock recovery back u can use ARI to do that but after the apxflash!!!
apx flash
Thanks for all your help but I can't seen to find the { V3 bootloader AND CWM Recovery package } that you mention. Can you lead me the right place for the files.
Thanks
Can I jump in here please as its sort of my problem as well.
Every thing goes fine ish.
When the tool tries to boot the tab into bootloader it fails.
Nothing on the tab screen. USB icon or computer disappears.
I just want to install a ics unlocked (is that the same as pateched) boot loader so I can install civs extreme???
Thanks
Why don't you guys read this thread.
http://forum.xda-developers.com/showthread.php?t=1688795
And install your Google USB drivers and verify they work with your tab in APX mode.
Later in the thread I posted an older app which installs Ver4 unlocked and CWM. Read the notes on my post's and give it a shot.
It's the app I always use.
MD
Okay. Rooted the A500 this afternoon... got ready to flash the first step from blackthund3r's APX Flash Utility... I have the drivers, up to date, and clicked "No" to go back and get them (accidentally) and now it is sitting still saying "Acer Iconia APX Mode" in the upper left screen in white text with a nice green ACER logo in the middle, but it isn't doing anything and the APX tool says "Waiting for 4 seconds for the tablet to enter the bootloader", but the tablet is not entering such a bootloader... What now?

Stuck at Green logo Oppo Screen Help please

I was trying to figure out how to root and put custom roms on so
I was watching a video and at one part they said to use "fastboot -w" which wipes userdata and cache.
Now when I boot my phone i get stuck at the green logo Oppo screen. Can't boot all the way.
I tried resetting it back to factory default, but didn't help at all.
I was trying to use 4.2.2 CyanogenMod 10.1
I have access to recovery mode and fastboot mode. But don't know what to do.
Please help me
I have the stock firmware but dont know how to flash it, I'd usually do it by recovery mode but I can't get the file on the phone to use it.
I got CWM on there now, but I just can't enable USB mass storage to get the new firmware in.
Fixed
Used the abd push/pull functions for show that stock firmware in the phone and use it. Worked like a charm.
Couldn't find the delete thread button.
/closed thread

[Q] LG G2 - Fastboot mode started udc_start

Hello everybody,
Last night i recieve update for my lg g2 d802 ( update to D80210c)
I downloaded and click install button on update. Phone rebooted and opened twrp. I had rooted device with twrp . After that i couldnt start phone OS, just starting twrp again and again . After that i click on restore to backup nandroid backup i have. It restored backup and than reboot system . After that i have just few words in top left angle :
450 Fastboot mode started
500 udc_started()
After i connect my usb cable have few more :
450 Fastboot mode started
500 udc_started()
660 -reset-
670 -portchange-
740 fastboot; processing commands
What should i do now, is this device completly bricked?
djordjesl said:
Hello everybody,
Last night i recieve update for my lg g2 d802 ( update to D80210c)
I downloaded and click install button on update. Phone rebooted and opened twrp. I had rooted device with twrp . After that i couldnt start phone OS, just starting twrp again and again . After that i click on restore to backup nandroid backup i have. It restored backup and than reboot system . After that i have just few words in top left angle :
450 Fastboot mode started
500 udc_started()
After i connect my usb cable have few more :
450 Fastboot mode started
500 udc_started()
660 -reset-
670 -portchange-
740 fastboot; processing commands
What should i do now, is this device completly bricked?
Click to expand...
Click to collapse
Good to know i wasn't the only one
Im just able to start researching now, i'll update if i find anything, but i assume there's some kind of command that can be given via adb to disable the fastboot and allow the phone os to resume functioning, as my logic indicates since the restore worked for you, your phone is now simply at a point with no attempted update. i did the same process of clicking reboot, twrp looping, restored a backup and twrp still looping
EDIT: Pretty sure it's going to be a flag in a flat file. Combing over my init.rc file now, and i found a strange file called smpl_boot with a single 0 in it, not sure what it does
BStinsonWhadup said:
Good to know i wasn't the only one
Im just able to start researching now, i'll update if i find anything, but i assume there's some kind of command that can be given via adb to disable the fastboot and allow the phone os to resume functioning, as my logic indicates since the restore worked for you, your phone is now simply at a point with no attempted update. i did the same process of clicking reboot, twrp looping, restored a backup and twrp still looping
Click to expand...
Click to collapse
Can you enter Download Mode? (Holding volume down when G2 is turned off and plug the USB)
I also experienced this when restore using TWRP. But fortunately I can flash back to stock.
BStinsonWhadup said:
Good to know i wasn't the only one
Im just able to start researching now, i'll update if i find anything, but i assume there's some kind of command that can be given via adb to disable the fastboot and allow the phone os to resume functioning, as my logic indicates since the restore worked for you, your phone is now simply at a point with no attempted update. i did the same process of clicking reboot, twrp looping, restored a backup and twrp still looping
Click to expand...
Click to collapse
I think you dont understand me, when i did restore twrp shows that restore was completed, and when i do a reboot it shows
450 Fastboot mode started
500 udc_started()
Now i cant do nothing with phone, i try to power off and turn on it just go to
450 Fastboot mode started
500 udc_started()
djordjesl said:
I think you dont understand me, when i did restore twrp shows that restore was completed, and when i do a reboot it shows
450 Fastboot mode started
500 udc_started()
Now i cant do nothing with phone, i try to power off and turn on it just go to
450 Fastboot mode started
500 udc_started()
Click to expand...
Click to collapse
ahh i misread your post thinking you somehow had status messages on your screen during boot and that you got into TWRP each time. the question above this post asking about download mode may help you
BStinsonWhadup said:
ahh i misread your post thinking you somehow had status messages on your screen during boot and that you got into TWRP each time. the question above this post asking about download mode may help you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2451696
specifically:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
fixed it for me for anyone finding this post that CAN get to TWRP, the above linked post has other hints as well that may work for OP
I got this same thing when I tried to update TWRP using flashify, I can reboot to phone , running CleanRom 2.0 but not to recovery in order to flash other stuff.
ossito2012 said:
I got this same thing when I tried to update TWRP using flashify, I can reboot to phone , running CleanRom 2.0 but not to recovery in order to flash other stuff.
Click to expand...
Click to collapse
I somehow managed to do this as well. Did you get yours working again?
Edit: Fixed it up with this APP (Note that 3 other similar apps did NOT work): https://play.google.com/store/apps/d...l.freegee_free
Yozzo1 said:
Hello everybody,
Last night i recieve update for my lg g2 d802 ( update to D80210c)
I downloaded and click install button on update. Phone rebooted and opened twrp. I had rooted device with twrp . After that i couldnt start phone OS, just starting twrp again and again . After that i click on restore to backup nandroid backup i have. It restored backup and than reboot system . After that i have just few words in top left angle :
450 Fastboot mode started
500 udc_started()
After i connect my usb cable have few more :
450 Fastboot mode started
500 udc_started()
660 -reset-
670 -portchange-
740 fastboot; processing commands
What should i do now, is this device completly bricked?
Click to expand...
Click to collapse
My situation is a little different than yours, but you may be able to do this method (which is what I am working on at the moment). As long as you can get into download mode.
http://forum.xda-developers.com/showthread.php?t=2432476
help !!
Hi, sorry for my english , I'm french
I wanted to flash a custom rom on my LG G2 D802 .
I wanted the Paranoid Android (PA +) with 4.3 JellyBean .
So I made the
Backup
Wipe data / factory reset
Wipe cache partition
Wipe dalvik Cache
After I
Choose zip ( custom ROM ) from sd card
Then I
Reboot System Now
And turn on my laptop, I get an error message saying
[640 ] started Fastboot Mode
[ 690] udc start ()
I realized I had to flash AOSP kernel before changing to a ROM paranoid . But my kernel is blocked and so I have to go back to the stock ROM
When I did this tutorial using lg tools , flashing stops at 49% with an error message .
I also saw that I could access the recovery mod by following this link http://forum.xda-developers.com/show....php?t=2565904(but I saw that I could not otherwise reboot my phone after it was bricking ) and therefore flash my stock Rom which I had made the backup . But I do not know if the ROM has been saved and if it remained in my files after the Wipes.
If it is not there, is that in buying a micro USB ====> HUSB adapter, I could install a stock ROM from a USB key ? Or is there a way I can put files from my computer to my laptop which has no port micro sd?
And is what I could with my kernel "blocked " ?
Thank you very much
Same problem here too. Can't get a recovery installed no matter what i do
Does anyone have a solution yet?? Same thing has happened to me.
If you can't go into download mode but get fastboot mode instead first repair download mode using http://forum.xda-developers.com/showthread.php?t=2477595 and than flash back to stock 4.2.2 using http://forum.xda-developers.com/showthread.php?t=2432476
My G2 can not go into download mode and recover mode, and my computer can not recognise it so I can not put anything to it.
fast boot
udc error.
CAN SOMEBODY
EXPLAIN IN SIMPLE WAY STEP BY STEP.
Thank you
Had this exact error too, fortunately flashing furnace kernel fixed it.
Tahir, I had to try several times until i succeed to boot to my recovery mode, try several times.
was having this issue. but i figured out my problem. the rom i was installing was a note3 rom. hahahaha. thats what happens when u have too many phones. and files in your computer. anyways.
i ddnt have to revert back to stock. i was able to reboot to twrp via hold power button and volume down buttons, when lg pops up, let go and press and hold both buttons again. when white screen with words comes up, press power then power then power. then ur back to twrp, at least mine did. and restored my recent back up.
nimrodsv said:
Had this exact error too, fortunately flashing furnace kernel fixed it.
Tahir, I had to try several times until i succeed to boot to my recovery mode, try several times.
Click to expand...
Click to collapse
How did you flash the kernel if you couldn't get into recovery?
I have download mode, but lg support tool only goes to 49% and I get error.
Would like to flash this kernel if you have another way
rodpgfx said:
How did you flash the kernel if you couldn't get into recovery?
I have download mode, but lg support tool only goes to 49% and I get error.
Would like to flash this kernel if you have another way
Click to expand...
Click to collapse
I could, after 5-6 times pressing Vol Down + Power method
nimrodsv said:
I could, after 5-6 times pressing Vol Down + Power method
Click to expand...
Click to collapse
I have similar issue after trying to install Xdabbed Camera on my LG G2 running with ClaudyG3 ROM.
I have flashed the Xdabbed Camera zip file sucessfully via TWRP 2.7.0.0 but when I reboot the phone after successful flashing the phone went into Fastboot Mode and UDC as mentioned above. Can my phone back again to recovery mode? I have backup ready, but only can restore if I can go into recovery TWRP...please help
epwt said:
I have similar issue after trying to install Xdabbed Camera on my LG G2 running with ClaudyG3 ROM.
I have flashed the Xdabbed Camera zip file sucessfully via TWRP 2.7.0.0 but when I reboot the phone after successful flashing the phone went into Fastboot Mode and UDC as mentioned above. Can my phone back again to recovery mode? I have backup ready, but only can restore if I can go into recovery TWRP...please help
Click to expand...
Click to collapse
Try booting to recovery after you charge your phone for at least one hour and while it's NOT CONNECTED to the computer
If that's doesn't help try using ADB

Reformatted /system, can't install new rom

I wanted to completely reformat my phone as my phone was buggy with Cyanogen Mod 12, so I formated everything.
The problem is that my PC was not detecting the drivers when in recovery mode, so I couldn't side-load with ADB, and I have no way of getting a .zip on to it.
I tried re-installing the clockwork mod using ODIN but it would just crash the application. I then tried heimdall and that said it installed it (I was hoping that it would fix adb)
Now I can't boot in to the clockwork mode recovery as it just instantly turns the phone off, however I can just boot normally in to the Galaxy S4 logo screen.
When I'm in the logo screen I do have access to ADB, however my phone is unathorised and I have no way to authorise it.
How can I A) fix clockwork recovery so it works again and B) put a zip on the phone or fix ADB detecting my device in recovery?
If you can get into download mode, flash a full stock ROM via Odin and start again
DSA said:
If you can get into download mode, flash a full stock ROM via Odin and start again
Click to expand...
Click to collapse
That worked great, thanks.
no probs, i find it to be a pretty good fall back in case of issues (just annoying reinstalling games etc..)

Categories

Resources