Related
I have rooted my EVO with the toast method and files. I updates my adb usb drivers and flash erecovery from my PC but when I download the file w/i RM and the DL finishes I select back up current rom and nothing happens. I did double check my root access by running the su command in a terminal and had no issues. I then DL'ed the file to me PC and transferred it to the root on the SD card, reboot into fastboot the manually into erecovery and tried to perform an update zip . Nothing is working as expected, does anyone have any ideas on things to try??? Also I am very familiar with RM as I used it all the time with my Droid.
dm5363b said:
I have rooted my EVO with the toast method and files. I updates my adb usb drivers and flash erecovery from my PC but when I download the file w/i RM and the DL finishes I select back up current rom and nothing happens. I did double check my root access by running the su command in a terminal and had no issues. I then DL'ed the file to me PC and transferred it to the root on the SD card, reboot into fastboot the manually into erecovery and tried to perform an update zip . Nothing is working as expected, does anyone have any ideas on things to try??? Also I am very familiar with RM as I used it all the time with my Droid.
Click to expand...
Click to collapse
Try just loading of Rom manager and click flash rec. All tht then try reboot into rec. May not work depending on what Rom your currently on
not sure what you mean
Are you suggesting reinstalling RM? Or are you suggesting DL'ing the Rom and flashing from RM?
Couple of things :
1) I have DL'ed the Rom from RM and began theflash process w/i the tool and nothing happens, where in the past on my droid it would go into CW recovery and flash the new Rom and all was well, but not thus far
2) I am still using the stock since UI and have flashed CW recovery via RM
3) the main thing I have noticed is the CW recovery isn't set for whatever reason
4) I did read in one of th xda threads that the boot loader was not able to be unlocked at this point
Long story short im a newb, im sorry for creating a new thread but ive exhausted my efforts looking for a solution to the problem im having. When the problem occured i had restored my original cwm backup that i created when first rooting my phone. I then did a factory wipe and reinstalled cwm and flashed my recovery. I went to install cm9 4-4-12 and i got a pop up that firmware update was available i clicked update system now and got sent to cwm recovery. Every time since then i cannot reboot into the android os, pulling battery. It doesnt matter what i do, ive tried to use a flash recovery zip i found in another thread to exit boot loop. Ive also tried restoring my original back ups and my recent back ups. I have the android sdk installed but having trouble getting adb to work not sure if i should go about trying to fix the recovery or trying to restore phone to its original state either way i think i need to get adb working before i can do either one. Any help is appreciated and im sorry if im wasting your time.
Did you try wipe cache, wipe dalvik cache, factory reset before flashing CM9?
Yes. The order i took was Wipe data/factory reset> Wipe cache partition> wipe dalvic cache> installed cm9 zip> installed gaps zip. still nothing got adb to work not doing much with it i know it has root access and when i got the state of the device it came up as unknown although im pretty sure im in recovery mode.
ok a few question and maybe a step by step to help you since i had a same promblem with a bad flash of CM9
1A. Can you boot into Recovery ? if not i can help you reflash your phone with the Kdz files took me forever to get it to work but i finilly found all the files needed.
1B. if it does boot into recovery run adb devices ... does it show the phone in recovery mode ? in the list.
If so then you can Download the following 6 files Dropbox Down link its not mine but was posted in another Nitro Recovery topic i will give credits once i re go threw the topic to see the poster
- recovery.img
- system.img
- baseband.img
- boot.img
- firmware.img
- pushall.bat
in your CWM recovery go to mounts or it may be under advanced and turn on usb mass storage and as long as all of those files are in your adb folder you can run the pushall.bat and it will place them on your sdcard.
After that turn off usb mass storage and run adb devices again to make sure you phone is still showing up. If so run these commands
Adb shell
****** notice the SU command isnt used here**** cant get super user in recovery but it will still let you run the commands and i can confirm it does work
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
if not then try to follow this for the CM9 Adb Drivers Wiki for CM adb drivers i know its a little work but it dose the trick then go back up to the previous step and try that to get to stock rooted
i dont think i left anything out but i can help with anything else i know if that doesnt get you back up and running.
Credits to ???? for the drop box link with the godly files for our nitro
and to Malnilion for his guide on unbricking the nitro
edit: re-ran superoneclick for run and it worked! I should be good from here
Got everything to work. Wait spoke to soon tried to reinstall firmware update again got the same problem. oh well guess i should done fw update before installing cwm. Thanks for the help i should be able to repete this problem in the case of another brick... which just occured.
So after going through the process of unbricking my phone a second time my phone was rebooted into software update screen. Updating firmware then software and did not have to go through factory reset. Strange...
I pushed all images to my device via adb,but ota update gets an error when trying to install. At least its not bricked. Anyone know of another method?
Sent from my LG-P930 using XDA
lg nitro in recovery loop
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Tokie the dropbox links are not working
reverendyummypants said:
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Click to expand...
Click to collapse
re push the img file back to the sdcard
adb push boot.img /sdcard/ make sure that he boot.img file is in the same folder as your adb and then try the dd command for it it happened to me once
EdwinXVS said:
Tokie the dropbox links are not working
Click to expand...
Click to collapse
im uploading to my own dropbox bare with me ill posyt a live link as soon as it ready guys
cwm recovery loop
_Tokie, retried. still dd command cannot be done. file not found. The files ARE IN the adb folder. Not sure what else to do.
when you type adb push boot.img /sdcard/ what does it say ? i dont see why it will do the rest and not that one
dd: can't open sdcard\boot.img : no such file or directory
i was asking about when you pushed the boot.img to teh sdcard... if yyou want i can look at it threw teamviewer total up to you ... if you deside that pm me then info for it
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
drumist said:
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
Click to expand...
Click to collapse
im going to assume that he is booting into CWM its thats the case with teh usb cable hooked to the computer he can turn on mass storage from the CWM and just tranfer it that way .. if he doesnt have a reader .. i just dont see why its not copying the boot image
I'm sorry. The files are on the sdcard. When it comes time for the dd command, i get that error which i recently posted.
If you're in CWM you have to ensure your sdcard is mounted. I have got caught up on this step as well lol
Thank you to all that helped! XDA is awesome! Everything is back to normal. It also helps to have the right / or \ lol
Download the zip from this link http://s000.tinyupload.com/index.php?file_id=70581848454313738691 . After that mount USB in PhilZ and copy over the zip file to your phone. Then flash the zip file and your boot loop should be fixed. The fix is originally by @fosunite and was posted on the PhilZ page.
Why is the file size so big?
arifqur said:
Why is the file size so big?
Click to expand...
Click to collapse
I put several ROMs in it that I modified to work with the old recovery which I also modded...all is in the zip make sure to read the readme
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
rob219 said:
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
Click to expand...
Click to collapse
That's basically what the tutorial says but it also has modified CM11 zips that will be flashable in twrp 2.6.1.0
This is a simpler guide for those who have trouble with terminal based solutions
Sent from my LG-E980 using Tapatalk
philz bootloop
rob219 said:
or you could just keep a twrp recovery zip on your sdcard and flash it like i did when philz recover kept booting into recovery.
Click to expand...
Click to collapse
I am having this same issue. everything was going fine with it when I booted into recovery from rom toolbox, but the first time I booted into philz with the power vol up and home it looped and I cant get out of it. This TWRP method that you mention what version of TWRP should I dl and please someone help soon my phone is out of commission.
rjmxtech said:
Hi all,
I recently figured out how to get an LG E980 back to a usable state after being stuck in a recovery loop due to a user or random system error from the PhilZ Touch Recovery (CWM/TWRP combo) and put CyanogenMod on it instead of having to flash back to stock.....the following link is directed to a zip file with a read me inside of it along with some files that have been modified to work with the recovery I have included in the zip file.
------HERE IS THE ZIP FOLLOW THE README INSIDE IT OR RISK BRICKING YOUR DEVICE------
******I am not responsible for anything that may happen to your device while following this guide, before following it, and after following it.......by downloading the zip file and following the steps you take all responsibility for anything that may possibly happen to your device at any time before, after, or while following this guide!!!!!!!!!!!!!!!!!!!!!!******
Click to expand...
Click to collapse
I successfully installed TWRP 2.6.1.0. Not sure oif it is related but when I try to flash the cm11 zip file it says "no MD5 file found". It still says the flashing was successful. I then flash the pa-gapps file and it says "successful".
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
droidbrain said:
I successfully installed TWRP 2.6.1.0. Not sure oif it is related but when I try to flash the cm11 zip file it says "no MD5 file found". It still says the flashing was successful. I then flash the pa-gapps file and it says "successful".
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
Click to expand...
Click to collapse
did the flashing take a few seconds? are the files you are flashing on the SD card? if the answer is yes to both, you need to move the files you want to flash to the internal storage, then flash them. Personally i prefer CWM to flash and go back to TWRP if i ever get stuck on a recovery bootloop(reboot to system, fix root when prompted).
I did fix that issue without his files.
droidbrain said:
so I reboot to system and i get the "secure booting error. Cause: Device Unlock, so Boot Successful" then it boots right back into TWRP.
Please help.
Click to expand...
Click to collapse
What you guys might need is a command which should put your phone on usable state.
In this case of a bootloop into recovery you just need 6 steps.
1. Download the aroma file manager. It has a build in terminal console. Get this one here:
http://forum.xda-developers.com/attachment.php?attachmentid=2231581&d=1378202418
2. Place the zip file on anywhere you like. On external sd it s easier to find. Let s put it on the root of external sd.
3. In the recovery please flash that zip file from step 1
4. After aromafm has started, press menu->open console .
5. A console appeared. Type this command all at once:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
6. Confirm this command by pressing enter. You see something displayed about copied with 1,1 kb or something. That was its process. To reboot your phone type in the console:
Code:
reboot
And confirm this by pressing enter again.
Info1: be sure that you didnt cause this boot loop by applying the OTA update from LG software update. If u did, the only way is to flash back with kdz!
Info2: Also if you flashed something what has caused an error loki ifying it and then bootloop, dont panic, use the command and flash something else working.
This command is handy, so write it down on paper or memorize it:.
Info3: If you enter the recovery by using POWER+volume up , ofc u need to enter the mentioned command in step 5 afterwards:::. Else you ll get a bootloop to recovery again.
Info4: If you are using philz touch recovery and have the aromafm zip file: Rename this file to "aromafm.zip" and place this into your external SD card into the clockworkmod/aromafm/aromafm.zip This way you can doubletap your recovery screen in philz touch and start your aromafm in a faster way.
Sent from my LG-E986 using XDA Free mobile app
fosunite said:
What you guys might need is a command which should put your phone on usable state.
In this case of a bootloop into recovery you just need 6 steps.
1. Download the aroma file manager. It has a build in terminal console. Get this one here:
http://forum.xda-developers.com/attachment.php?attachmentid=2231581&d=1378202418
2. Place the zip file on anywhere you like. On external sd it s easier to find. Let s put it on the root of external sd.
3. In the recovery please flash that zip file from step 1
4. After aromafm has started, press menu->open console .
5. A console appeared. Type this command all at once:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc bs=1 count=1088
6. Confirm this command by pressing enter. You see something displayed about copied with 1,1 kb or something. That was its process. To reboot your phone type in the console:
Code:
reboot
And confirm this by pressing enter again.
Info1: be sure that you didnt cause this boot loop by applying the OTA update from LG software update. If u did, the only way is to flash back with kdz!
Info2: Also if you flashed something what has caused an error loki ifying it and then bootloop, dont panic, use the command and flash something else working.
This command is handy, so write it down on paper or memorize it:.
Info3: If you enter the recovery by using POWER+volume up , ofc u need to enter the mentioned command in step 5 afterwards:::. Else you ll get a bootloop to recovery again.
Info4: If you are using philz touch recovery and have the aromafm zip file: Rename this file to "aromafm.zip" and place this into your external SD card into the clockworkmod/aromafm/aromafm.zip This way you can doubletap your recovery screen in philz touch and start your aromafm in a faster way.
Sent from my LG-E986 using XDA Free mobile app
Click to expand...
Click to collapse
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
droidbrain said:
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
Click to expand...
Click to collapse
What did u do before u got in a bootloop?
Sent from my LG-E988 using XDA Free mobile app
droidbrain said:
When I flashed zip it went into file manager and I had to acess the terminal from the menu. After the command string was entered I did get the 1,1 kb file message. When I tried to enter reboot, I got sh: reboot: not found. I exited console and closed file manager. It put me back into twrp. I then reboot back to system but I got the same secure boot message and back into twrp.
Click to expand...
Click to collapse
You don't reboot from the console, you exit the console and also exit Aroma file manager back to CWM and then you just reboot system from Philz CWM and that should end your bootloop. Done it a bunch of times and always gets me out of the bootloop.
Erik
fosunite said:
What did u do before u got in a bootloop?
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
I was installing the OTA ATT update. When the phone restarted it booted into twrp been stuck there since. I can get into download mode but thats about it.
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
ricco333 said:
You don't reboot from the console, you exit the console and also exit Aroma file manager back to CWM and then you just reboot system from Philz CWM and that should end your bootloop. Done it a bunch of times and always gets me out of the bootloop.
Erik
Click to expand...
Click to collapse
That is exactly what I did. Only boots into twrp.
droidbrain said:
I was installing the OTA ATT update. When the phone restarted it booted into twrp been stuck there since. I can get into download mode but thats about it.
---------- Post added at 05:28 PM ---------- Previous post was at 05:19 PM ----------
That is exactly what I did. Only boots into twrp.
Click to expand...
Click to collapse
Then your problem is not the recovery, your phone is booting to recovery only because your ROM fails to boot. Try installing another ROM using TWRP to see if it fixes your problem.
Erik
ricco333 said:
Then your problem is not the recovery, your phone is booting to recovery only because your ROM fails to boot. Try installing another ROM using TWRP to see if it fixes your problem.
Erik
Click to expand...
Click to collapse
I have tried multiple roms and have had the same problem. The only rom that seemed to be successful is the one attached to the link in the beginning of the thread. Except it still gave me the secure boot message and booted into twrp.
droidbrain said:
I have tried multiple roms and have had the same problem. The only rom that seemed to be successful is the one attached to the link in the beginning of the thread. Except it still gave me the secure boot message and booted into twrp.
Click to expand...
Click to collapse
What I would do in your case is restore back to stock using LG Flash Tools and then start over with FreeGee and install the recovery from there and see if your trouble clears.
Erik
Read info1 from my post.
U aplied the update and then u cannot boot. So u must flash kdz back to stock.
Sent from my LG-E988 using XDA Free mobile app
fosunite said:
Read info1 from my post.
U aplied the update and then u cannot boot. So u must flash kdz back to stock.
Sent from my LG-E988 using XDA Free mobile app
Click to expand...
Click to collapse
How do I do that?
droidbrain said:
How do I do that?
Click to expand...
Click to collapse
Better is that u should read this topic on the OP in the following link:
http://forum.xda-developers.com/showthread.php?p=44983841
[Guide][Stock Roms] Return Back To Stock AT&T & International
Sent from my LG-E988 using XDA Free mobile app
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2.
Note: A more detailed and user-friendly version of these instructions can be found at: http://www.oppoforums.com/threads/n5206-international-root-instructions.24159
Download http://lum.uk/n3/files/recmodn3.img and http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
Copy the rooter onto your SD card.
Boot into fastboot by holding volume up while powering on the phone.
fastboot oem unlock
fastboot flash recovery recmodn3.img
fastboot boot recmodn3.img
Flash the root coloros zip file, reboot and you're rooted.
Note: This is a modified stock recovery that can flash OTAs as well as zips not signed by Oppo. If you prefer TWRP then that is available here: https://dl.twrp.me/n3/. Note that at the time of writing TWRP is unable to flash OTAs.
Thanks to [email protected] for the original root method, Arvin A. [email protected] for the fixing SuperSU to work on ColorOS, and [email protected] for providing the modified N3 recovery.
Restoring stock firmware
Download your chosen firmware and recovery from this thread
Copy the firmware to the root of the internal storage
Take a nandroid backup using TWRP
Reboot to bootloader from within TWRP
Code:
fastboot flash recovery recovery_N3.img
fastboot reboot
adb reboot recovery
Use the stock recovery to flash your chosen firmware
If you are downgrading then wipe data and cache (you did remember to take a nandroid, right?)
Reboot
You are now on stock fimware. Follow the rooting instructions in post #1, and if you wiped you may optionally restore only the data partition from your nandroid backup.
Will memory be erased?
Hi,
So i'm looking forward to root my beautiful Oppo N3.
On my last Phones memory (data and so on) was erased alongside with unlocking the phone.
Will it be the same on this phone so that I have to backup all my data?
Your data will not be erased when rooting or unlocking. Also your warranty will not be invalidated like it is with other manufacturers.
It is, however, always wise to take a backup before anything like this, just in case something does go wrong.
Hi,
I tried rooting my N3 now but i made a mistake by not executing the commands after falshing SuperSU.
That's why my phone is always booting into TWRP. There i tried executing your commands, but apparently the shell refuses to su by throwing exception: "command not found"
Going on with mount-command, it is also giving back an error: "can't find /system in /proc/mounts"
Hope sb could help me now...
EDIT: Solved by installing stock recovery, booting system, and the reflash twrp.
Lum_UK said:
Even simpler root than Invisiblek's method for the older versions: If you have already tried that method and now have broken wireless, see Post #2
Download http://teamw.in/project/twrp2/282 and http://download.chainfire.eu/supersu
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery openrecovery-twrp-2.8.4.0-n3.img
fastboot reboot
adb reboot recovery
Flash Super SU from within TWRP. Then boot the OS
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and you're rooted.
By default ColorOS doesn't let apps auto-start themselves, so go into security centre and allow SuperSU to auto-start, otherwise you won't get prompts for root when other apps need it.
Thanks to invisiblek for the original root method and babelmonk for the fix. I have shamelessly copied these and adapted them for the new firmware.
Click to expand...
Click to collapse
Quoted from your post in oppo forum
Wait for the phone to boot:
adb reboot recovery
It should boot into TWRP recovery flash the SuperSU zip you downloaded but do not reboot as we need to fix a small bug in SuperSU due to Oppo not using the expected startup scripts.
adb shell
su
mount -o remount,rw /system
echo "/system/xbin/su --daemon &" >> /system/etc/init.qcom.post_boot.sh
Reboot and congratulations. You are now rooted.
Sorry , quite new in fastboot command so i apologize if I misunderstood you but I'm running on N5206_EX_23_150208 , which should i follow ? to boot up after flashing SuperSU or not to boot up ?
It doesn't matter which way around you do it, just that root won't work outside of ADB until it's done.
I assume that XDA folk are more familiar with ADB etc. than on the Oppo forums so the instructions skip over more detail here.
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Lum_UK said:
Updated the method to use fastboot boot instead of fastboot flash.
This should work around the issue with phones that can't flash twrp, and also leave the stock recovery in place which is more useful to have until we get some custom roms.
Click to expand...
Click to collapse
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Anilexis said:
I was using modified boot.img to get root and then edit init.qcom.post_boot.sh. Now my wi-fi is broken. Can I fix it without wiping? Maybe flash some other boot img?
Click to expand...
Click to collapse
Fixed it by flashing boot.img from 150208, root still there due to script edit.
Updated the OP to use the modified stock recovery (Wmjan's recovery for the N5207) as this will be friendlier to noobs and also make it easier to install OTAs.
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
cowabunga said:
Anyone know where to get the root coloros file? Link doesn't seem to work for me...
http://www.oppoforums.com/attachment..._v2-zip.31142/
Click to expand...
Click to collapse
Sorry for the delay in replying. I've re-hosted the file for you.
http://lum.uk/n3/files/Root_ColorOS_by_tantrums_v2.zip
You could also try this. It worked on my girlfriend's R5 running a similar version of ColorOS. Didn't need modified recovery or anything, install it, run, click the root button, and it'll reboot to recovery and root for you.
http://lum.uk/n3/files/ForceRoot.apk
can this root work with Chines n5207
Hello,
I'm from Malaysia,
I got problem with my N3 / N5206 after update the newest version of software...now it cannot detect any line signal and open a wifi...what the problem,can u help me...
I can't make the WiFi to work again. Installed all versions of firmware and no luck....
Update: I was using the wrong tool to flash the firmware.
Don't update the phone with Msm8974DownloadTool !!!!
You have to download and install QPST_2.7.460 and place the phone in download mode by pressing volume + and power button and then in QPST load the firmware N5206EX_11_A.11_150528_SVN6225 or Oppo_N3_N5206_EX_11_A.13_151230 or N5206EX_11_A.10_150519_SVN6196
After flashing the wifi is working but you gonna loose the NV ram backup for the IMEI numbers..
Then you have to open dealpad with *#801# and anable Full-port ON
In QFIL(QPST) click on Tools then click QCN Backup Restore
Choose the qcn file and press restore.
Everything will work again after reboot the phone...
I recently picked up a new-to-me LS970 after an unfortunate encounter with gravity :/
I went to root/unlock the phone and all seemed to go well. I loaded TWRP 2.6.3.0 and proceeded to make a backup of my stock rom/settings/ESN. I then attempted to flash a new ROM and found that the MIUI port wasn't functional for me. I tried to flash CM12 as well but cannot get past the setup wizard.
Unfortunately, TWRP doesn't recognize my backup. If I go to the file manager, I can see the directory and files that compose my backup, but if I go to restore it, I get a blank menu with no restore options.
The ADB sideload option fails to connect (It says 'Starting ADB sideload feature...' forever until I cancel it) and I cannot get far enough into either ROM to enable me to push files over MTP. in CM12, I can get ADB to see my phone (appears when I use 'ADB devices') but if fails to push a file due to permission being denied.
What are my options here? How can I move forward with having a functional phone?
I was able to tinybin my way back to TWRP 2.6.0.0 and that has allowd me to ADB push files. Sideload still will not function. I tried flashing several ROMs but they always fail. I treid reformating my SD card, and that also fails (unable to read partition table). Any guess as to what is going on? MIUI successfully works now, so at least I'm through the worst of it.
LordKyleOfEarth said:
I recently picked up a new-to-me LS970 after an unfortunate encounter with gravity :/
I went to root/unlock the phone and all seemed to go well. I loaded TWRP 2.6.3.0 and proceeded to make a backup of my stock rom/settings/ESN. I then attempted to flash a new ROM and found that the MIUI port wasn't functional for me. I tried to flash CM12 as well but cannot get past the setup wizard.
Unfortunately, TWRP doesn't recognize my backup. If I go to the file manager, I can see the directory and files that compose my backup, but if I go to restore it, I get a blank menu with no restore options.
The ADB sideload option fails to connect (It says 'Starting ADB sideload feature...' forever until I cancel it) and I cannot get far enough into either ROM to enable me to push files over MTP. in CM12, I can get ADB to see my phone (appears when I use 'ADB devices') but if fails to push a file due to permission being denied.
What are my options here? How can I move forward with having a functional phone?
Click to expand...
Click to collapse
LordKyleOfEarth said:
I was able to tinybin my way back to TWRP 2.6.0.0 and that has allowd me to ADB push files. Sideload still will not function. I tried flashing several ROMs but they always fail. I treid reformating my SD card, and that also fails (unable to read partition table). Any guess as to what is going on? MIUI successfully works now, so at least I'm through the worst of it.
Click to expand...
Click to collapse
If it is your original TWRP backup (TWRP that Freegee installed) it might not restore, I had that problem a long time ago. Try installing an updated TWRP, that one is really old at this point.
If you have an updated TWRP you can mount MTP from recovery and transfer any files to your internal storage. I suggest starting out with the stock ZVC so you can have a fully working stock device and make sure everything works. From there you can copy zips to your device and flash away.
If you have issues copying a recovery to your device you can always use adb to flash. I believe it is
"fastboot flash recovery (name of recovery.img)" without quotes or parenthesis.
EDIT: On the CM 12 setup thing, @Shelnutt2 just posted in the CM12 thread that the bug is fixed and will be pushed to tonight's nightly.
Here is a newer recovery built by an international dev but this is the one I used when I had the OG.
http://dl.kevinjoa.me/recovery-geehrc/twrp/