Hi my 1st post on the forum been browsing for a couple of weeks after getting my XT890 & as I like to mod/hack everything I own, So decided to unlock & root my Razr I ..
I successfully unlocked the boot loader without issue, & proceeded to root it,(usb debugging mode) then I came across problems tried various methods motofail2go on my x86 pc but had problems with the MTP driver not installing?
So tried the batakang method on my Win7 x64 pc only when I run the batch file all seemed well until the phone rebooted to fastboot & started to download. there it stuck on downloading... no response for several minutes.
I reattempted the procedure numerous times, & had to restart my phone & cause of flash failure on fastboot with an error like downloaded -1 bytes download failed,
So I had to RSD lite an retail GB firmware tried both (31 & 39) to restore the phone I read there are some issues with rooting on 39 but still got the same problem on 31?
I have searched & cannot find an answer to why it wont root?
Do I need a sd card in the phone for the hacks to work that is the only reason I can think of but seems unlikely, I have the latest drivers ect installed tried various fastboot commands to reflash the boot.img ect but same problem it wont download to the phone & I have to RSD recover.
I would like to thank the people & members of the forums for the information I have already read & hopefully shall receive :good:
Related
Hey guys,
I think I might have bricked my phone. I've installed yesterday a new firmware (device is s off, rooted). Version 6.09.401.5. So far so good. Downloaded a new ROM. Wiped everything including sdcard in twrp, then tried to push the rom to the sdcard. Also worked. But, I can't install it. Tried 100 different recoveries. It keeps me saying that it can't mount /system. Tried another firmware, but this time it failed (don't know why, it hang on the RUU screen, and windows didn't detect my m7 anymore). So i tried to boot in the bootloader (I think the firmware update failed..) I get the normal bootloader screen, but now fastboot isn't working anymore. My phone get's recognized by adb in recovery, but nothing other than that. i tried to install another rom again, but this time it sais that /cache /system etc. are unmountable. What have I done? Can someone help me or did I just brick the device?
Yeah, this means I can't get by no means inside the RUU environment, so I can't flash a new firmware. The phone doesnt get recogdnized by Windows in the bootloader, however the bootloader screen is normal. So can't use fastboot.
Okay, little update guys. Picked up a Windows 8 machine (mine was running on 8.1) So fastboot works. Tried to flash firmware, but now it sais remote: not allowed. Any idea's? Tried 2 different firmware packages.
Alright! Got it fixed. Here's the solution:
Thanks to Windows 8.0, not 8.1, i was able to flash a firmware, so that windows recognized the phone again. Then, picked up a flashable firmware zip (~1GB) and flashed it via the standard procedure. I think that that repartitioned the whole device, so that the original rom could be installed via the firmware.
My phone is rescued again, thanks xda!
batuhanxtx said:
Alright! Got it fixed. Here's the solution:
Thanks to Windows 8.0, not 8.1, i was able to flash a firmware, so that windows recognized the phone again. Then, picked up a flashable firmware zip (~1GB) and flashed it via the standard procedure. I think that that repartitioned the whole device, so that the original rom could be installed via the firmware.
My phone is rescued again, thanks xda!
Click to expand...
Click to collapse
Did you just have a 6 post conversation with yourself and change your name on the 7th post ?
Most people here know about windows 8.1 and fastboot
a little reading would have saved you a lot of stress
Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock ROM.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
Came back to it after a few weeks and issue has been resolved. Despite error warnings fastboot operated correctly, only manually. Any script etc. that booted device into fastboot would never find the device. Simple as flashing recovery and restoring a backup.
tl;dr: I'm not very bright.
FiniteDGk said:
Hey all, thanks for reading. I've caught myself in a predicament. I can solve most issues that crop up my way, but right now I'm a bit stuck. It is likely fairly simple and I am just dumb...
The huge issue here is that I am running stock lollipop for the D415 model. I am having the typical base-band and WiFi issue that a lot were having. Like most, I just booted up into TWRP and restored a backup. I Wanted to try again so I flashed the stock ROM and tried again; didn't work...oopss..
LG Flash Tool refuses to locate my device. Download mode fails to connect my device properly. Error is:
EP1/out FAIL nfo=40 pg0=ffbd880
usb_read() transaction failed
So now I am stuck with a broken stock ROM, no TWRP, and no current way to re-flash a stock KDZ.
Steps taken so far:
1. Reinstall all drivers
2. Attempt to root and install TWRP to access my backups (No access to Download mode)
3. Started all over with original USB.
What can I do? Thank you again for reading my long post.
EDIT: Forgot to include that I see the proper devices in device manager.
EDIT 2: Device is properly configured and can be found in ADB when powered on.
Click to expand...
Click to collapse
where u able to fix it? i currently have no recovery or OS it just stays at the LG screen i can only get into Download mode i tried to flash a kdz but it cant read my phone....it turns on but thats it i cant got past the LG screen and when i connect my phone now i get different device drivers than before like LGE AndroidNet USB Serial Port and USB Modem....idk what to do
I've had my Verizon LG G2 for almost a year and mistakenly upgraded to Lollipop. I researched downgrading to KitKat and it looked safe; I had dual booted my HP Touchpad with a similar process.
I tried rooting with ADB, but it was giving me fits. I used the LG One Click Root Tool. It worked fine. (Running on Windows 7.)
I installed TWRP v2.8.5.1, and downloaded a stock version of KitKat 4.4.4. (I'll admit, at this point, I had looked at multiple guides. Many had missing links or dead ends, but they were all about the same, and always stock.) I followed instructions on clearing and wiping caches, etc. I believe the exact ROM I tried to install was VS98011A_01.zip. It didn't work. It gave the error:
"assert failed: run_program("/tmp/loki.sh") ==0
E: Error executing updater binary in zip"
I looked for more ROMs and tried ParanoidAndroid "pa_g2-4.0-ALPHA-20131203-vs980.zip". At this point, I started to worry and tried installing the Gapps file I downloaded with the stock ROM, and it installed with no problems.
I then tried to install a newer version of TWRP "twrp-2.8.6.0-vs980.zip". (Again, I hadn't really found any great guides at this point, especially to fix my problem, so I was assuming there was something wrong with my ROMs.) It didn't work, and I tried to install Cyanogen Recovery because I ran across it and remembered it from my HP Touchpad. "cm-10.2-vs98012b.zip" did not work, and gave the error above.
I looked for Loki issues and tried downloading a fresh Loki (sorry, I don't have the link) folder and replaced all the files in the original KK .zip I tried. Same loki error. (Sometimes I'll get a "sysMapFile" error, but not often. At this point, I'd dragged a lot of things over to try to install and get anything to work.)
At this point, I tried the following:
http://forum.xda-developers.com/showthread.php?t=2448960
http://forum.xda-developers.com/showthread.php?t=2451696 (as well as a similar one by downloading a laf.img)
http://forum.xda-developers.com/showthread.php?t=2797190
http://forum.xda-developers.com/showthread.php?t=2432476
http://hackerspace.lifehacker.com/how-to-install-a-rom-via-sideload-1505153925
http://forum.xda-developers.com/showthread.php?t=2318497
http://www.androidayos.com/2014/10/06/fix-bricked-lg-g2-stuck-logo-twrp-bootloops-download-mode/
http://forum.xda-developers.com/showthread.php?t=2448960
There were definitely some more links I used but these were the most promising and the ones I still have open.
Several of the LGFlashTools were very close to working, but there were several issues:
1. I can't get it into Download Mode, as it gives a boot certification error.
2. There were some problems with the phone not showing up in Device Manager under "Ports" with COM41, and I thought I had largely resolved that issue. (Depending on the article I was looking at.)
3. Drivers, I'm not sure if they're an issue; I've downloaded several, and installed them, including 2.0 and a 3.1.
ADB does not recognize my device, as I've tried sideloading, although I can still drag and drop files. (I believe I pushed a file into the device early on and it worked though.)
4. Fastboot recognizes there's a device and can boot it via CMD but will not give a number when I use "fastboot devices". I've researched some flashing via Fastboot, and tried flashing the original KK .zip with it, but it said there wasn't enough space. I have about 14GB left on a 32GB device, however.
I hope I've provided enough information, because I've researched and tried so many ways to unbrick it, short of physically opening the phone as suggested here: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Any advice or suggestions would be greatly appreciated. I would love to know what I did wrong, because I know custom ROMs would be a great alternative to dealing with Lollipop until I can upgrade over a year from now.
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
carkev said:
I nearly bricked my Razr i XT when downgrading from a Kitkat update to JB 4.1.2 but thanks to the great work here I am making some progress but cannot get Recovery or Root. the unlocking of bootloader via the Motorola website went fine and thanks to this post
http://forum.xda-developers.com/showthread.php?t=2239706 I got the rom I wanted, and it's fine.
I have read many other tutorials on installing a recovery and have downloaded and tried 6 or 7 CWM and TWRP images
but it never completes - fastboot says it has, but the phone stubbornly hangs at the flashing.
I have no problems getting into fastboot, but failed many times, and in desperation have tried with USB debugging on and off
and with and without sim and sdcard inserted.
attached are some photos to show where I am stuck at, and I would greatly appreciate some help
Click to expand...
Click to collapse
U said fastboot hangs at flashing the recovery, but on the command lines on your PC it says finished. Have u tried booting into recovery?
What recovery did u use and where did u get it?
USB debugging, simcard and sdcard don't have anything to do with fastboot. But it is likely that u didn't know that
thanks for looking at this.
I did try booting into recovery from my PC by after rebooting it and then taking the recovery option, but the phone hung at the Motorola bootloader unlocked warning screen.
this link was typical of the various tutorials I used: http://androidteen.com/motorola-razr-i-how-to-root-and-install-clockworkmod-cwm-recovery-on-android-4-1-2-jelly-bean-firmware/
to be fair I cannot recall where I got all the recovery images from - I have that many, and had to rename them recovery.img, so cannot remember the original download names
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
carkev said:
update:
I have just tried an app from the google play named Root Android, which advised trying other apps - Kingroot, Framaroot & Towelroot,
but they all failed .
what did catch my eye yesterday was the yellow text when in fastboot that says 'dismatched partition entry'
I ignored it as the img files I was trying to flash are all much smaller than the 100mb stated,
but today I am beginning to think that perhaps my recovery partition is corrupt and look for ways to repair it.
does that make any sense?
Click to expand...
Click to collapse
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Hazou said:
That could be it. Try flashing a rsd lite package from JB. Than go to the recovery and see if u have stock back.
Click to expand...
Click to collapse
thanks HazouPH, I'll give that a go
I have solved my problem with CWM:victory:
whilst I am not 100% certain I am pretty much sure it was a driver problem - for those who this may benefit, here is what I did.
1. I did not reflash my phone, but stayed with the one in my original post.
2. remember that the main problem was that Fastboot said I had succeeded in flashing a Recovery image, but that the phone 'hung'
at flash as in my photo. and then from my phone I could not get to recovery from the fastboot menu .
3. I stumbled across a posting (on XDA, but I cannot remember where) that said the Motorola drivers were not as good as they should be and that the Motohelper one's would be fine - so I downloaded them, and have attached the zip below.
4. I then decided to tidy up my PC and uninstalled all mobile phone drivers, plus any redundant USB Device drivers
5 for the USB tidying up I tend to use USBdview, which is superb and can be found here
6 when all this was done I simply tried the reflash of CWM - and got the same situation I had been having all along
but amazingly, when I selected 'recovery' it went in CWM - I nearly fainted with surprise!
from all this I can only assume it was a driver problem as I had changed nothing else.
perhaps it was Motohelper drivers- perhaps it was USBdview that did it for me - I will never really know, nor care!
I now have CWM v6.0.1.9 - it is touchscreen and permanent, plus I use the cute Reboot by app by Petrus to control my phone.
happy days!
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. After reading some people on forumes saying that this device might not have a locked bootloader, I finally thought that this tablet did not have its bootloader locked. Then I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
I finally used heimdall and was able to flash all the partitions with the stock images. Now I am back in stock version. I would like to flash a TWRP recovery.
Can someone tell me if I have to unlock the bootloader with this device ? If it is, how can unlock it ? I can not find anything in the settings developer section, and can not use a call number input in order to enter a system code as it's a tablet. Do I have to wipe something from the stock recovery in order to see it ?
Thanks for your time.
Hi -yo-.
You don't need to do OEM unlock as this device is so old.
Also twrp-3.2.3-0-lt02ltespr.img is NOT for this device.
For recovery look from here and for ROM here.
Thanks jonezy82 for the answer. Indeed, I figured all of that out.
I decided to get it back stock and not trying to flash anything custom.
Thanks for your time.