Develop Bugs

[Q] installed Sper wipe before copy rom.zip to sdcard

I isntalled Super Wipe to my htc one x before load rom.zip to sd card :S now cant open phone or recovery mod :S so how can i load stock rom again help please

rover_x said:
I isntalled Super Wipe to my htc one x before load rom.zip to sd card :S now cant open phone or recovery mod :S so how can i load stock rom again help please
Click to expand...
Click to collapse
First you will need to reflash your recovery while your phone is in fastboot mode, you can do this by opening a cmd and using the command 'fastboot flash recovery recoveryfilehere.img' and changing recoveryfilehere for your recovery file's name.
I am a bit unsure on these next steps but I believe you will then need to boot into the recovery you just installed and then use the following commands.
'adb devices'
'adb shell'
'mount sdcard'
and then in another cmd you will use the command 'adb push ROMNAME.zip /sdcard
then reboot into recovery and look for your ROM in the root of your sd card and install it as usual. Don't forget to flash the kernal too.

I tried these steps but didnt get result

See http://forum.xda-developers.com/showpost.php?p=26119526&postcount=17 and adapt to yours.

i tired many times , but each time get message " error:device not found" :S

Do you have HTC USB driver installed ?

yes i did

So it means that you're successfully boot into recovery by fastboot boot recovery.img and adb not working for you ?
Please note, adb will not work when you do fastboot flash recovery recovery.img

ckpv5 said:
So it means that you're successfully boot into recovery by fastboot boot recovery.img and adb not working for you ?
Please note, adb will not work when you do fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Ah right, my bad
Sent from my HTC One X using xda premium

How to push files in fastboot or Recovery?

Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?

Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2

JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.

RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.

Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars

Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps

If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.

mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.

Then just use the sideload, it works quite well for me.

mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250

in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave

GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.

No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement

stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone

[Q] Galaxy Nexus Root and Fastboot not working

My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!

sonshadsil94 said:
My Sprint Galaxy Nexus Jellybean is not rooting and will not flash a recovery. Here is what i did before the problem
Installed the Samsung Drivers
Installed and set up ADB and SDK tools
unlocked my bootloader
flashed TWRP recovery
Made a Nandroid Backup
flashed a rooted rom that was apparently for ICS (but I didn't know at the time)
These were all per qbking77's root method for Sprint Galaxy Nexus. After I flashed the rom I waited for 20 minutes for my phone to reboot and it never did. So I pulled the battery and went back into the recovery. I restored my original backup and rebooted successfully. I decided to attempt flashing the rom (that I didn't know wasn't meant for my software) again. This time when i went into recovery mode, the picture of the android with the caution symbol appeared, meaning that there was no recovery found. Now when I attempt to reflash TWRP recovery or any recovery for that matter (Now using the Galaxy Nexus toolkit for Jellybean) the program says
sending 'recovery' <xxxx KB>
FAILED <remote: Invalid command>
finished. total time: 0.012s
An Error Occurred.
and on the phone side for TWRP it says FASTBOOT STATUS - download 0055d000
and for Clockwork mod touch it says FASTBOOT STATUS - download 004c8000
Before I do anything but plug my phone into the computer, the phone says FASTBOOT STATUS - FAILInvalid Command
Since this started happening I have tried
Re-Locking and unlocking the bootloader
Uninstalling and reinstalling the toolkit
uninstalling and reinstalling the drivers
Factory resetting my phone
Is my phone just unrootable now? Please someone help!
Click to expand...
Click to collapse
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.

Petrovski80 said:
The "picture of the android with the caution symbol" is the stock recovery. You booted into android after restoring your nandroid. During that boot, android automatically reflashed the stock recovery which overwrote TWRP. To prevent this, you need to rename or remove either the stock recovery image or the script that will flash it on boot. Look at the 101 & FAQ post linked in my signature to find out where these files are.
As for unable to flash a custom recovery, don't use a toolkit. Just use fastboot from the commandline.
Click to expand...
Click to collapse
I know where the files are, but how am I supposed to remove or rename them without root access?

sonshadsil94 said:
I know where the files are, but how am I supposed to remove or rename them without root access?
Click to expand...
Click to collapse
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250

bk201doesntexist said:
just remount /system on recovery, either by adb shell, either by the recovery menu after fastboot flash. boot the recovery directly from bootloader.
after /system is rw, through 'adb shell', custom recoveries have a pre-rooted/busyboxed environment, which allows you to do maintenance. this is the mount command to run in adb shell:
'mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system'
then just remove the files, 'umount /system' when you're done, reboot.
sent from my i9250
Click to expand...
Click to collapse
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?

sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.

sonshadsil94 said:
When I try to flash a custom recovery using command prompt, it gives me the same error message as when using the toolkit. So, how do you do it with adb shell?
Click to expand...
Click to collapse
whats the exact fastboot command you're using to flash twrp?
problem was you made a backup of stock, which has files that restore, on boot, the stock recovery.
sent from my i9250

efrant said:
What are you trying to do exactly? I've read the entire thread, and I'm confused. If you want to go back to stock, look at the "flash" link in my sig. If you want to root, look at the "root" link. If you want to know about mounting /system, look at the "basics" link.
Click to expand...
Click to collapse
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.

sonshadsil94 said:
I tried your root method, and clockwork mod booted up, but the version of superuser that you linked to failed, so i rebooted my device and downloaded the jellybean version of superuser. When I tried to restart clockworkmod using the same method as before, I got the error message you see in the picture.
Click to expand...
Click to collapse
Try using a different USB cable, and try using a different port on the back of your PC.

efrant said:
Try using a different USB cable, and try using a different port on the back of your PC.
Click to expand...
Click to collapse
I tried both of those just now, with the same error message as before.

sonshadsil94 said:
I tried both of those just now, with the same error message as before.
Click to expand...
Click to collapse
The only thing I can think of is flash the LC03 bootloader. Try flashing that first, and make sure you have the latest version of fastboot. Then try again.

would running terminal in windows with admin privileges help?
sent from my i9250

Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2

deeren said:
Use the command
fastboot flash recovery cwm.img
And not fastboot boot cwm.img as seen in the screenshots and see if it works this way.
If not try to do a fresh install of everything
Use fastboot erase.... to wipe everything and Fastboot install ...to install everything from scratch.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
thanks deeren, i asked him what was the exact command he was using, that error had to be syntax error.
sent from my i9250

Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.

sonshadsil94 said:
Thanks all you guys but what actually ended up happening was I successfully booted into clockworkmod touch recovery since that was the only one my phone hadn't blocked yet. While in recovery i flashed supersu (the right version) and rebooted. It asked if I wanted to remove the files that flash stock recovery on boot and I selected yes. Well that didn't do jack crap, so with my newly acquired superuser powers, I deleted the files i needed to. Then I tried to flash another recovery, but they were still giving me errors. So here is the process I took completely out of luck and hopefulness that I knew what I was doing. From the command prompt with my phone in fastboot, I typed "fastboot flash recovery cwmt.img". this gave me the same "fastboot <remote: invalid command>" error, so I typed the same command and it once again gave me the "sending xxxxkb" message where it would sit on that same line until I killed the program. So I did kill the program and opened another command prompt in the same folder. I typed the same command for the third time, and everything went smoothly from there. I'm currently rooted and running Cyanogenmod 10. Once again, thanks to everyone who helped I greatly appreciate it.
Click to expand...
Click to collapse
please edit the title of the thread to include the tag "[SOLVED]".

bk201doesntexist said:
please edit the title of the thread to include the tag "[SOLVED]".
Click to expand...
Click to collapse
How do you edit the title?

I have same problem to...

sonshadsil94 said:
How do you edit the title?
Click to expand...
Click to collapse
Edit first post?
Sent from my i9250

[Q] Phone stuck at HTC One Beats Audio screen

Hi, I'm having a problem with the phone freezing on booting D:
Unlocked the bootloader.
Installed ClockworkMod recovery.
Made a backup.
[Not sure] rooted it.
I tried to install a ROM [CyanogenMod 10.1], but that made the phone freeze on the HTC screen instead, so I tried to restore the backup, but now I'm stuck on the HTC One Beats Audio screen & ADB won't recognise the phone is connected [I've got the drivers & it worked before].
Can anyone offer any help? Would be greatly appreciated.

Make a full wipe in the recovery then install the CM10.1, gapps and the vendors ! Don't reboot....go from the recovery to the bootloader
Adb reboot bootloader
Then flash the boot.img from the CM10.1
Then reboot the phone !

Mr Hofs said:
Make a full wipe in the recovery then install the CM10.1, gapps and the vendors ! Don't reboot....go from the recovery to the bootloader
Adb reboot bootloader
Then flash the boot.img from the CM10.1
Then reboot the phone !
Click to expand...
Click to collapse
Thanks for the reply.
I can't get ADB to recognise that the phone is attached to the PC though, despite having the latest drivers [HTC Sync] & the fact that it worked earlier. I've done kill-server & start-server a hundred times.
Any idea why what I've tried so far would make it unable to be found?

Hold the power and the volume - button together until the phone reboots into the bootloader, from there you can go in to the recovery and mount the sdcard as a mass storage device. Copy the needed files and do as i described in my first post.
You don't need adb, you need to perform fastboot commands in the bootloader. The rest is done in the recovery

Mr Hofs said:
Hold the power and the volume - button together until the phone reboots into the bootloader, from there you can go in to the recovery and mount the sdcard as a mass storage device. Copy the needed files and do as i described in my first post.
You don't need adb, you need to perform fastboot commands in the bootloader. The rest is done in the recovery
Click to expand...
Click to collapse
I already have a CM10.1.zip on the device, so erased the cache & flashed boot.img from that in the bootloader, then went into recovery & installed the .zip, but it's still bootlooping, just on the HTC screen this time though.

You need to flash the vendor installer in recovery also... find it in cm10.1 thread.

Mr Hofs said:
install the CM10.1, gapps and the vendors !
Click to expand...
Click to collapse
Install :
CM10.1
GAPPS
VENDORS
please read carefully
VENDORS

Mr Hofs said:
Install :
CM10.1
GAPPS
VENDORS
please read carefully
VENDORS
Click to expand...
Click to collapse
Okay, thanks for the help people!
I'm having an issue with getting the files onto the device to flash them now though. As I said, I had ADB working [how I got the CM.zip on there], but now it isn't & as there's no removable media for this phone, I don't know how I can get these onto the phone D:
In the device manager, it recognises the phone as a ADB thing, but checking the devices [adb devices] returns nothing.
I tried mounting USB in recovery but I got 'unable to open ums lunfile'.
Any ideas? Thanks again for the help so far.

CWM is out of date.
DL this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Copy to fastboot folder and rename recovery.img
Phone into fastboot mode, type fastboot flash recovery recovery.img
Then mount and it works.

TToivanen said:
CWM is out of date.
DL this: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
Copy to fastboot folder and rename recovery.img
Phone into fastboot mode, type fastboot flash recovery recovery.img
Then mount and it works.
Click to expand...
Click to collapse
Perfect, this did the trick! Big thanks

Good !
CASE CLOSED !

Recovery Explaination If Poss...

Hi
Have One x on H3G_001 and updated to jb (Hboot 1.39).
Forgot to nandroid backup (rushing doesn't pay!) and when I attempted to go to cwm recovery I was presented with blank screen.
Have tried TWRP (JB Version) and that works but as no usb mounting available cannot place nandroid onto phone storage.
All this has occurred since phone has had screen replaced.
Is this a case of coincidence or have the kernels changed on recoveries (ICS to JB), I'm totally baffled!
PS: Thanks to Mr. Hofs for assistance he has given so far regarding this, and if anyone has seen JB RUU for Three UK direction would be appreciated :fingers-crossed:.

My suggestion would be to flash any rom in order to use ums and after that transfer and restore a backup. Does adb work on twrp? You could push the file like this: adb push C:\derp.zip /sdcard/
Plan b would be using cwm blindly with hardware keys and someone assisting.

You can use fastboot to boot right into recovery.
Fastboot boot recovery_file_name.img
There is also a nandroid back up thread here on xda.
Sent from my HTC One X using xda app-developers app

TToivanen said:
My suggestion would be to flash any rom in order to use ums and after that transfer and restore a backup. Does adb work on twrp? You could push the file like this: adb push C:\derp.zip /sdcard/
Plan b would be using cwm blindly with hardware keys and someone assisting.
Click to expand...
Click to collapse
ADB works, but no good with command script. (Not sure how to structure command in cmd)
What is ums please?

UMS = USB Mass Storage

passion8059 said:
Hi
Have One x on H3G_001 and updated to jb (Hboot 1.39).
Forgot to nandroid backup (rushing doesn't pay!) and when I attempted to go to cwm recovery I was presented with blank screen.
Have tried TWRP (JB Version) and that works but as no usb mounting available cannot place nandroid onto phone storage.
All this has occurred since phone has had screen replaced.
Is this a case of coincidence or have the kernels changed on recoveries (ICS to JB), I'm totally baffled!
PS: Thanks to Mr. Hofs for assistance he has given so far regarding this, and if anyone has seen JB RUU for Three UK direction would be appreciated :fingers-crossed:.
Click to expand...
Click to collapse
Hey,
Copy your rom .zip to the adb directory.
Boot into recovery mode, open cmd cd into your adb directory and type:
adb push romname.zip /sdcard/
Flash, reboot

davidk-il said:
Hey,
Copy your rom .zip to the adb directory.
Boot into recovery mode, open cmd cd into your adb directory and type:
adb push romname.zip /sdcard/
Flash, reboot
Click to expand...
Click to collapse
Yeah ....that's the problem, he can't see the recovery so installing a rom with the recovery is pretty difficult

passion8059 said:
Hi
Have One x on H3G_001 and updated to jb (Hboot 1.39).
Forgot to nandroid backup (rushing doesn't pay!) and when I attempted to go to cwm recovery I was presented with blank screen.
Have tried TWRP (JB Version) and that works but as no usb mounting available cannot place nandroid onto phone storage.
All this has occurred since phone has had screen replaced.
Is this a case of coincidence or have the kernels changed on recoveries (ICS to JB), I'm totally baffled!
PS: Thanks to Mr. Hofs for assistance he has given so far regarding this, and if anyone has seen JB RUU for Three UK direction would be appreciated :fingers-crossed:.
Click to expand...
Click to collapse
Mr Hofs said:
Yeah ....that's the problem, he can't see the recovery so installing a rom with the recovery is pretty difficult
Click to expand...
Click to collapse
TWRP seems to work for him just fine just no USB mounting

davidk-il said:
TWRP seems to work for him just fine just no USB mounting
Click to expand...
Click to collapse
Sorry.....time for bed, to sleepy

Mr Hofs said:
Sorry.....time for bed, to sleepy
Click to expand...
Click to collapse
Good night

passion8059 said:
ADB works, but no good with command script. (Not sure how to structure command in cmd)
Click to expand...
Click to collapse
Haha just copy the ROM zip file onto your C drive and rename it derp. Then copy and paste my command to your adb command prompt and press enter.

TToivanen said:
Haha just copy the ROM zip file onto your C drive and rename it derp. Then copy and paste my command to your adb command prompt and press enter.
Click to expand...
Click to collapse
Thanks all to those who helped out.
Managed to get phone working again by push zip via adb.
Only prob I have is phone is not detecting any networks so will go and have antenna checked out.
Thanks again!

You did flash the boot.img of the rom you installed, no?
Sent from my IceCold One X using xda premium

TToivanen said:
You did flash the boot.img of the rom you installed, no?
Sent from my IceCold One X using xda premium
Click to expand...
Click to collapse
yes
tried three seperate roms incl;uding stock nandroid and nothing

Hey,
Did you fastboot erase cache after flashing boot.img?
Sent from my HTC One X using xda app-developers app

davidk-il said:
Hey,
Did you fastboot erase cache after flashing boot.img?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
yes

passion8059 said:
yes
Click to expand...
Click to collapse
How about running RUU ?
fastboot getvar version-main
post the output here

davidk-il said:
How about running RUU ?
fastboot getvar version-main
post the output here
Click to expand...
Click to collapse
cant do ruu route as on h3g_001 and 3.14.771.1 not available

passion8059 said:
cant do ruu route as on h3g_001 and 3.14.771.1 not available
Click to expand...
Click to collapse
How about wiping and starting from scratch?

You can use fastboot to boot right into recovery.