Related
Hi
Would it be possible for me to do the above without having to connect my phone to my laptop every time?
I know I have would have to load the boot.img first from a cmd window whenever i wanted to try a new rom, but was just wondering if I'd have to do that with it already on the internal sd card.
Any help would be appreciated.
Wiggo
Unless the backup you're restoring uses the same boot.img as the one you're using you will need to flash the one from your backup (using fastboot) when you restore it.
Recovery doesn't have permission to write to the boot partition; this means whether you're flashing a ROM or a backup from recovery the boot.img won't be written and you'll have to do it manually.
hopscotchjunkie said:
Unless the backup you're restoring uses the same boot.img as the one you're using you will need to flash the one from your backup (using fastboot) when you restore it.
Recovery doesn't have permission to write to the boot partition; this means whether you're flashing a ROM or a backup from recovery the boot.img won't be written and you'll have to do it manually.
Click to expand...
Click to collapse
That makes sense. Thanks very much for your help
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Any suggestions on how I can get access back to my device so I can repair/replace the platform.xml file and restore functionality to my phone?
Thank you very much!
Deozaan said:
Hi folks,
I tried to modify the platform.xml file to enable some write permissions. As far as I can tell, the app I used to modify the file didn't write it back correctly, and now my device is what might be called "semi-bricked."
Almost everything force closes, WiFi and write permissions seem to be broken, and I can't seem to get my Galaxy Nexus to communicate with my PC via USB.
I tried booting into CWM and mounting some /system, but I'm not sure how to access it since fastboot/adb don't seem to recognize the device.
I've also booted into some sort of recovery (fastboot?) that looks like the attached image. But I can't get it to do anything except boot up into the normal OS when I click the power button.
Click to expand...
Click to collapse
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
enryea123 said:
No it is not bootloader. to access to the bootloader turn on your device long pressing power, volume up and volume down buttons together (don't use odin).
To access to cwm recovery from bootloader just press volume down button until you see "recovery" option, then press power button and it will boot in recovery.
which rom are you using?
solution: download the zip file of your rom and extract the file you modified, make a zip (if you can't make a flashable zip i'll post an attachment for you) and flash it in recovery
Click to expand...
Click to collapse
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Deozaan said:
Thanks for the reply.
I actually did manage to get my PC to recognize the device via USB/adb and I copied the file back to the way it should have been. But that didn't fix anything, so I ended up doing a wipe/factory reset. Everything works now but things still seem a bit. . . off. For instance, it takes a while after my phone boots up before the WiFi will actually connect. It used to be connected almost immediately. And it takes a while for the alarm icon to load/show up in the notification area at the top. And I can't find the option in the settings anymore to use USB debugging. There are lots of little things like that, where it works, but it just doesn't quite work like it used to. . .
And to answer your question, I'm using the stock ROM that came with the Galaxy Nexus (from Google Play Store).
Click to expand...
Click to collapse
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
enryea123 said:
first: to make the "developer settings" appear go settings/About phone and tap on build number 7 times (google has hidden it in 4.2).
said that, you can:
1) fix permissions in cwm recovery (under advanced menu)
2) download a zip of your rom and flash it in recovery
3) if your bootloader is unlocked (you see a padlock when you boot your phone) you can flash a factory image to return completely stock.
4) if your bootloader is locked you can follow the 3) method but you will lose all your sdcard data.
Click to expand...
Click to collapse
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Deozaan said:
Thanks again for the response.
I got developer settings to appear. Hooray! Fix Permissions is one of the first things I did to try to repair the platform.xml file when things were broken. I ran it again (but from ROM Manager rather than from CWM Recovery) and it didn't seem to have any effect on the weird sluggishness when first booting up.
My bootloader is unlocked. Will I have to root again if I flash one of those factory images? I'm currently backing up the contents of my "SD card" in case I have to completely wipe the entire thing.
Click to expand...
Click to collapse
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
having a backup of the sdcard is always a good idea :good:, i have 2 backups of mysdcard on 2 different hard drives of my computer and the pictures i take with the camera are automatically uploaded on my dropbox .
enryea123 said:
well, you can firstly try to flash a zip of your rom (search on xda or google), it should fix.
the fastboot flash method is the google method so you won't need root (you just have to go into fastboot and connect your phone to your computer, doesn't matter if you have root, or a different rom/kernel/recovery).
If you don't know you to flash from fastboot try first to flash the rom zip.
Click to expand...
Click to collapse
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Deozaan said:
Weird things are happening. I was making a backup of the "SD Card" and partway through, things stopped copying over. And pretty much everything got erased from it. No big deal, since I'd already copied the important stuff first.
But CWM Recovery won't flash the zip file. It keeps telling me the update failed. I verified the hash on the zip I downloaded and it is the same as what is listed on Google's site. But it just won't flash in CWM.
Click to expand...
Click to collapse
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
enryea123 said:
wait, are you in cwm recovery o just in stock recovery (they are different)? have you previously installed a cwm recovery using fastboot? which zip are you trying to flash?
edit: ok you know what is rom manager so i think that you are in cwm.
edit2: try this zip
Click to expand...
Click to collapse
I was in CWM Recovery. I was using the zip file that I extracted from the link you gave me for Google's stock ROMs (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
enryea123 said:
edit2: try this zip http://goo.im/devs/bigxie/maguro/bigxie_maguro_OTA_JOP40D-signed.zip
Click to expand...
Click to collapse
Try this one
Deozaan said:
I was in CWM Recovery. I was using the zip file that I extracted from here the link you gave me (I can't post external links yet):
(Factory Images "takju" for Galaxy Nexus "maguro" (GSM/HSPA+) (with Google Wallet) --> Android 4.2.1 (JOP40D))
Strangely enough, after "failing" to flash the zip, I had to log into my Google account again because I had selected the option to Wipe Data and Cache, and most things seem to be working very well again. One odd thing I'm still noticing, though, is that some things don't seem to be syncing properly. For example, if I archive some of my email in the Gmail app, then log into Gmail on my PC, the mail is still unread in my inbox. My phone downloads the new mail just fine. But the changes I make on my phone (reading, archiving, deleting, etc.) don't seem to be syncing to anywhere else.
I'm downloading the zip you suggested. I'll give that a try. Thanks!
Click to expand...
Click to collapse
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
enryea123 said:
That is not a flashable zip! It is a factory image, it must be flashed via fastboot using a computer.
Click to expand...
Click to collapse
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
I got it working again. The ROM you gave me failed signature verification in CWM Recovery, but I told it to install anyway and it worked. Thank you.
The problem I was having with Gmail not syncing was that I used Titanium Backup to restore my data, but because all the data from my "SD card" got erased, Titanium Backup itself lots its settings, so my Device ID was different. I guess Gmail relies on the device ID for syncing.
Thank you so much for your help! I learned a lot from the experience.
Glad i helped you. well this is one of the reasons why i don't restore data with titanium (especially system data).
and by the way:
Deozaan said:
Just to be sure I explained myself clearly, I downloaded that Google provided factory image (a .tgz file) and inside it I found a zip file named "image-takju-jop40d.zip" which is what I tried to flash.
That said, I've just recently finished downloading the one you just suggested to me and I will give that one a try soon. Thank you again for your help. I really appreciate it.
Click to expand...
Click to collapse
To fully reset and install a clean rom using fastboot you have to extract the bootloader-blabla.img and radio-blabla.img files from the tar.gz archive and then extract the 4 .img files inside the zip (that is inside the tar.gz) and flash this 6 .img files connetting your phone in bootloader mode to your computer and using fastboot in terminal (in fact this procedure reinstall the recovery too).
I was getting random reboots and I tried to delete everything. I thought "clean to install new ROM" would just do a thorough cleaning.
When I try to boot it stays on the white HTC screen.
I can boot into the recovery and Squabbi's HTC One M8 toolkit reads it.
However, I have no idea what files to flash or even HOW to flash them so I can get an OS back on my phone. Can somebody please help?
I have no ADB experience.
Copy a rom zip on external sd and flash it through recovery or use a nandroid backup if you have one, but as you want a clean install maybe you want to use the first method
lukes91 said:
Copy a rom zip on external sd and flash it through recovery or use a nandroid backup if you have one, but as you want a clean install maybe you want to use the first method
Click to expand...
Click to collapse
Thank you for your reply. I am currently in ADB i tried to do "adb sideload" but got an error "failed to write data 'protocol fault (no status)'
I am going to try "adb push" right now and see if that works.
In the meantime, is it possible for me to recover using RUU in my current state of being stuck in recovery mode? Thanks again. I'll make sure to hit that donation button.
decko5 said:
Thank you for your reply. I am currently in ADB i tried to do "adb sideload" but got an error "failed to write data 'protocol fault (no status)'
I am going to try "adb push" right now and see if that works.
In the meantime, is it possible for me to recover using RUU in my current state of being stuck in recovery mode? Thanks again. I'll make sure to hit that donation button.
Click to expand...
Click to collapse
Well, the error might be a recovery issue, a cable issue (use stock htc one) or a driver issue... Unfortunately no RUU is available, so search for a nandroid backup in mr hofs' thread, copy it on the external sd card and recover it... Use the same recovery the backup was taken with (should be noted near the backup)... Let me know if you need further help dude
lukes91 said:
Well, the error might be a recovery issue, a cable issue (use stock htc one) or a driver issue... Unfortunately no RUU is available, so search for a nandroid backup in mr hofs' thread, copy it on the external sd card and recover it... Use the same recovery the backup was taken with (should be noted near the backup)... Let me know if you need further help dude
Click to expand...
Click to collapse
Ok so i found my nandroid backup and i am currently i am in adb. how do i push the backup to the TWRP backup directory?
decko5 said:
Ok so i found my nandroid backup and i am currently i am in adb. how do i push the backup to the TWRP backup directory?
Click to expand...
Click to collapse
It's easier to mount the storage in twrp, so you can browse it with the computer and copy paste the file inside... Then unplug the phone and restore the nandroid...
Edit: in this thread
http://forum.xda-developers.com/showthread.php?t=2318497
there are very useful infos for you, and there is the adb push command you are looking for (path should be the same)... Let me know if you recover everything or if you need more help
lukes91 said:
It's easier to mount the storage in twrp, so you can browse it with the computer and copy paste the file inside... Then unplug the phone and restore the nandroid...
Edit: in this thread
http://forum.xda-developers.com/showthread.php?t=2318497
there are very useful infos for you, and there is the adb push command you are looking for (path should be the same)... Let me know if you recover everything or if you need more help
Click to expand...
Click to collapse
I flashed TWRP via fastboot. then i pushed a nandroid backup hosted on this site to the /sdcard/TWRP/backsups/<a directory i made here> finally got everything working. Thanks again for everything. I just hope the random rebooting doesn't come back.
I think it was rebooting because I disabled some bloatware apps via an app called App Master, which requires root. And when i restarted the phone, all those apps tried to run again but there was a conflict with App Master.
decko5 said:
I flashed TWRP via fastboot. then i pushed a nandroid backup hosted on this site to the /sdcard/TWRP/backsups/<a directory i made here> finally got everything working. Thanks again for everything. I just hope the random rebooting doesn't come back.
I think it was rebooting because I disabled some bloatware apps via an app called App Master, which requires root. And when i restarted the phone, all those apps tried to run again but there was a conflict with App Master.
Click to expand...
Click to collapse
Well, you can try to reinstall the rom without removing the bloatware... If it's stable you found the culprit
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...
Good morning,
I don't know why but my current phone status is that doesn't boot anymore with Android installed on it. At the moment I've my phone unlocked, twrp 3.1.1 and a backup of last S.O.
I took (when unlocking) a complete full_dump.img as described in the thread UnlockBootloader correctly, with all other files also.
Now, I'm able to enter in TWRP, so I place these operatinos:
wipe all
restore backuped twrp zip
restart phone in normal booting
All operation seems to works fine but when I restart the phone it goes back in TWRP... no android boot window. I watched the content of phone and it seems no files where placed in system (it seems void).
What's the matter?
I'm able to go in fastboot mode also (download mode it working but my PC can't recognize the COM port at the moment)
Help me please, I'd like to restore the complete full_dump.img (and return with locked status var) with the command:
send_command \\.\COM19
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Anyone help me please?
I tried many time to install a .ZIP custom image ROM, but it doesn't seem to boot with android because all times come back in TWRP.
Sounds like you wiped system, edited it, deleted something or it is corrupt.
Wipe everything excluding system ( don't check it off)
Go advanced > fix permissions
Install a ROM again
If that doesn't work. I suspect you have a file system anymore.
You will now have to go backwards, reinstall stock image using lg bridge if you didn't make a backup of stock with the file system
Romulus76 said:
Good morning,
I don't know why but my current phone status is that doesn't boot anymore with Android installed on it. At the moment I've my phone unlocked, twrp 3.1.1 and a backup of last S.O.
I took (when unlocking) a complete full_dump.img as described in the thread UnlockBootloader correctly, with all other files also.
Now, I'm able to enter in TWRP, so I place these operatinos:
wipe all
restore backuped twrp zip
restart phone in normal booting
All operation seems to works fine but when I restart the phone it goes back in TWRP... no android boot window. I watched the content of phone and it seems no files where placed in system (it seems void).
What's the matter?
I'm able to go in fastboot mode also (download mode it working but my PC can't recognize the COM port at the moment)
Help me please, I'd like to restore the complete full_dump.img (and return with locked status var) with the command:
send_command \.\COM19
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Click to expand...
Click to collapse
You can use FWUL ( https://tinyurl.com/FWULatXDA ). Go into LG folder and double click on the lglaf auth icon.
Once you see the terminal window use your restore command:
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Next time you should consider to use the DLM backup method ( https://tinyurl.com/dlbackup )
Regarding TWRP try the latest beta in the official TWRP thread.
Try to format system in the wipe menu then flash a custom ROM again. Pull the recovery log afterwards as described in the TWRP FAQ 4 A of the official TWRP thread.
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
You can use FWUL ( https://tinyurl.com/FWULatXDA ). Go into LG folder and double click on the lglaf auth icon.
Once you see the terminal window use your restore command:
dd if=/data/media/0/full_dump.img of=/dev/block/mmcblk0 bs=4096 count=1552384
Next time you should consider to use the DLM backup method ( https://tinyurl.com/dlbackup )
Regarding TWRP try the latest beta in the official TWRP thread.
Try to format system in the wipe menu then flash a custom ROM again. Pull the recovery log afterwards as described in the TWRP FAQ 4 A of the official TWRP thread.
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I'd try this method first. Steadfaster is more credible and knows what he us talking about before you try my suggestion and wipe data as well.
His method is to restore the file system... And to make a backup of it in case it happens again
---------- Post added at 08:11 AM ---------- Previous post was at 08:06 AM ----------
BTW I'm using twrp 3.1.1 works fine but your phone might not like it
deltadiesel said:
Sounds like you wiped system, edited it, deleted something or it is corrupt.
Wipe everything excluding system ( don't check it off)
Go advanced > fix permissions
Install a ROM again
If that doesn't work. I suspect you have a file system anymore.
You will now have to go backwards, reinstall stock image using lg bridge if you didn't make a backup of stock with the file system
Click to expand...
Click to collapse
Yes, it sounds like something was corrupt in the file system or similar.
I tried to install a new custom ROM (as many other times in the past), wiping data - cache - system first but with no luck, it wont boot Android, and return always in TWRP.
Yesterday evening I tried also a full KDZ refurbish with LGUP since my phone can boot in download mode (and recognized from LGUP), but with no luck because after start the process the tool give me a message back (at 9% of operation):
"FAIL - Flash error code 0x2000"
Is there any method to repair corrupted file system or flash partition? TWRP o similar?
steadfasterX said:
Next time you should consider to use the DLM backup method ( https://tinyurl.com/dlbackup )
Regarding TWRP try the latest beta in the official TWRP thread.
Try to format system in the wipe menu then flash a custom ROM again. Pull the recovery log afterwards as described in the TWRP FAQ 4 A of the official TWRP thread.
Click to expand...
Click to collapse
Thanks,
but when I made the full_dump.img there wasn't this DLM method out yet (I made this on the 11/16/2015)
I'll try the new beta TWRP on the official thread late this evening, and I'll try to make a LOG...
Thread update: my phone doesn't go in recovery mode also, now only in DOWNLOAD MODE (volUP + USB cable) and it hangs on error 0x2000
I think I'll take the phone to the LG customer care, for motherboard change.
You are getting 0x2000 because you are trying to flash a KDZ with an older ARB version than what is currently on your phone. You need to flash newer firmware that has the same or greater ARB version than what is on your phone.
-- Brian
Romulus76 said:
Thread update: my phone doesn't go in recovery mode also, now only in DOWNLOAD MODE (volUP + USB cable) and it hangs on error 0x2000
I think I'll take the phone to the LG customer care, for motherboard change.
Click to expand...
Click to collapse
You are flashing the wrong file for your phone
Flash another one
After you success fully flash right file( try one that is biggest in size and most recent)
Flash TWRP (3.1.1 should be fine after)
MAKE A BACKUP OF EVERYTHING (data, system, firmware, etc - so you don't have to go through this again just in case)
Wipe ( don't wipe system - you can do a regular wipe without checking things off it doesn't select system)
Install custom ROM
Flash SuperSU to root again
https://forum.xda-developers.com/showthread.php?t=3660257
Post 71-75