Hi Guys,
I generally make do with all of the older threads (and google), but for this I just
had to make an account and ask if there is some saving possible.
I reinstalled (Flashed) the stock rom for the J5 (with ODIN), rooted the phone using j5nlte Auto Root.
flashed TWRP and then MOAB & SuperSu. This is where something seemed to go wrong
as TWRP asked me again if I wanted to install SuperSu when exiting. Stupidly I swiped
instead of choosing no. This is where my phone ended up in a bootloop to TWRP.
Now my first reaction was, okay no biggie i'll just wipe the phone and start over again. All of a sudden
Odin can't recognize the phone when I reboot into bootloader, because it doesn't go into the normal
Samsung DOWNLOAD MODE anymore, I get the following if I choose to reboot into bootloader
ODIN MODE
Product name: SM-J500FN
Current Binary: Custom
System Status: Custom
FRP Lock: Off
Knox warranty void: 0x1 (4)
RP SWREV: S1, T1, H1 R1, A1, P1
Secure Download: Enable
the pc doesn't recognize it in this state.
In TWRP it adb does recognize it. It seems to recognize adb commands.
tried the following
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
but it gives me an error message: failed to allocate 910 blocks, out of space?
anymore options?
Forgot to mention:
When I try to wipe using TWRP or install from TWRP I get the error
E: unable to mount '/data'
everydaychap said:
Forgot to mention:
When I try to wipe using TWRP or install from TWRP I get the error
E: unable to mount '/data'
Click to expand...
Click to collapse
what TWRP you have?
vaserbanix said:
what TWRP you have?
Click to expand...
Click to collapse
twrp v2.8.7.0
everydaychap said:
twrp v2.8.7.0
Click to expand...
Click to collapse
install TWRP 3.0.2.0
that 2.8.7.0 have bugs
you can get that in my signature
Basic & Useful information
that thread with TWRP 2.8.7.0 is old
vaserbanix said:
install TWRP 3.0.2.0
that 2.8.7.0 have bugs
you can get that in my signature
Basic & Useful information
that thread with TWRP 2.8.7.0 is old
Click to expand...
Click to collapse
I wish I could, but Odin does not recognise my Phone and within TWRP I can't install anything.
everydaychap said:
I wish I could, but Odin does not recognise my Phone and within TWRP I can't install anything.
Click to expand...
Click to collapse
Reinstall the drivers in pc
Maybe will help
Trimis de pe al meu SM-J500F folosind Tapatalk
vaserbanix said:
Reinstall the drivers in pc
Maybe will help
Trimis de pe al meu SM-J500F folosind Tapatalk
Click to expand...
Click to collapse
it just goes back to the same ADP windows driver when I uninstall
everydaychap said:
it just goes back to the same ADP windows driver when I uninstall
Click to expand...
Click to collapse
i see it is recognized in adb
try to push the recovery.img with adb
vaserbanix said:
i see it is recognized in adb
try to push the recovery.img with adb
Click to expand...
Click to collapse
it recognises adb commands, but with fastboot it says <waiting for device>
which adb command could I use to push recover.img?
Yes you can.
On adb help
You get instruction how to "push" a file
Trimis de pe al meu SM-J500F folosind Tapatalk
adb push -p recovery.img recovery
Trimis de pe al meu SM-J500F folosind Tapatalk
I got it to work.
did the adb push and afterwards was able to install version 3 of TWRP. Then was able
to somehow reformat the internal drive, because at first it showed 0kb. Then installed
stock rom again and it's working now.
Delete this post pls
Related
can someone help me please, i have tried to install cm13, and i did a clean wipe, now it is saying no os installed, and i couldnt even find the restore package !!! how can i load os into my oneplus two, as yo all knw we dont have a external memory card, am nt sure how to load os into phone now !!! some please help !!
devveda said:
can someone help me please, i have tried to install cm13, and i did a clean wipe, now it is saying no os installed, and i couldnt even find the restore package !!! how can i load os into my oneplus two, as yo all knw we dont have a external memory card, am nt sure how to load os into phone now !!! some please help !!
Click to expand...
Click to collapse
Are you on TWRP 3.0.x.x?
If yes, then go to Mount Section, enable MTP.
Connect to your PC, transfer desired ROM.zip and flash.
If no TWRP, then reboot to BootLoader/Fastboot
Download latest TWRP from official website, then flash it using command:
fastboot flash recovery twrp.img
fastboot reboot (keep holding vol- to enter TWRP)
where "twrp.img" is name of the recovery file.
WhyOrean said:
Are you on TWRP 3.0.x.x?
If yes, then go to Mount Section, enable MTP.
Connect to your PC, transfer desired ROM.zip and flash.
If no TWRP, then reboot to BootLoader/Fastboot
Download latest TWRP from official website, then flash it using command:
fastboot flash recovery twrp.img
fastboot reboot (keep holding vol- to enter TWRP)
where "twrp.img" is name of the recovery file.
Click to expand...
Click to collapse
yes i tried to enable mtp, but nothing was shown in computer to transfer !!!
thank god used sideload and installed stock rom, its fine and all set nw !!!!
devveda said:
yes i tried to enable mtp, but nothing was shown in computer to transfer !!!
Click to expand...
Click to collapse
Try with Latest TWRP build.
And at worst case scenario use Qualcomm Recovery Tool to go back to OOS 2.1.1, as already you have lost all your data.
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
devveda said:
thank god used sideload and installed stock rom, its fine and all set nw !!!!
Click to expand...
Click to collapse
Oki Good, Enjoy!
Can you help me with something? When I again try to reboot my device in recovery I couldn't find the twrp recovery or any type of recovery, after installing the twrp, it's not rebooting, am getting a message saying "booting.... Failed <remote: dth not found>, I couldn't install twrp recovery can u help me with this?
Hey guys,
i've a massive problem with my G4. Today i flashed TWRP on the device, after i was unlocking the bootloader. After booting up into TWRP, and installing SuperSU, I just restarted it. Now it's dead. Seriously, it's dead.
I can't start it at all. If I plug in a USB-Cable, i just see the LED Light. I've Windows, and at my Device Manager, the G4 is recognized as QHSUSB_BULK.
I saw a Thread for the Moto G (1th), and i'm pretty sure, that i can't to this like in this tutorial:
http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Is there any option, what i can do?
@Marwycy are you able to boot into bootloader and TWRP..?
Keep volume and power key pressed for about 2 minutes,
And then if you made any backup restore it, otherwise flash stock...
__Madddy said:
@Marwycy are you able to boot into bootloader and TWRP..?
Keep volume and power key pressed for about 2 minutes,
And then if you made any backup restore it, otherwise flash stock...
Click to expand...
Click to collapse
At first i wasn't but, i found a thread with a solution:
http://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943
Now i can boot into the Bootloader, i deleted TWRP with fastboot, to flash the stock firmware from the motorola support site.
But its not working yet.
After "fastboot flash -S 1900M system system.img" I just get the error: "cannot load system.img". If I just use "fastboot flash -S 1800 system system.img", fastboot is going to flash, but stopped with the error:"(bootloader) data size exceeds download buffer. The last error seems to be logical, the file is bigger than 1800MB..
I'll try to flash each files which are in the image.
Marwycy said:
At first i wasn't but, i found a thread with a solution:
http://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943
Now i can boot into the Bootloader, i deleted TWRP with fastboot, to flash the stock firmware from the motorola support site.
But its not working yet.
After "fastboot flash -S 1900" I just get the error: "cannot load system.img". If I just use "fastboot flash -S 1800 system system.img", fastboot is going to flash, but stopped with the error:"(bootloader) data size exceeds download buffer. The last error seems to be logical, the file is bigger than 1800MB..
Click to expand...
Click to collapse
Are you sure your downloaded firmware is correct with your phone model no. and carrier..?
For Flashing Stock,
Follow this thread, post 4 (restore to stock)
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
__Madddy said:
Are you sure your downloaded firmware is correct with your phone model no. and carrier..?
For Flashing Stock,
Follow this thread, post 4 (restore to stock)
http://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
Click to expand...
Click to collapse
I tried it, i can't open system.img at all. So i can't extract anything..
Marwycy said:
I tried it, i can't open system.img at all. So i can't extract anything..
Click to expand...
Click to collapse
System.img ???
Are you trying to flash "dumped system" ...??
It will not get flashed that way, you need to download complete firmware, download links are there on which link I provided first..
Download correct firmware and follow that guide..
__Madddy said:
System.img ???
Are you trying to flash "dumped system" ...??
It will not get flashed that way, you need to download complete firmware, download links are there on which link I provided first..
Download correct firmware and follow that guide..
Click to expand...
Click to collapse
Sorry, i was a bit confused because of this large list of commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
Click to expand...
Click to collapse
And i figured out, that it's not necessary. All I had to do ist following the official way by just using "fastboot system system.img" , with the Image from the officla Motorola website. My first file was corrupt, that was the problem.
Now my phone is working again
Thanks for help.
Marwycy said:
Now my phone is working again
Click to expand...
Click to collapse
For Rooting, don't flash zip directly,
Follow this guide, https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
Take BACKUP, if anything wrong then RESTORE it...
first upgrade to 7.0 bro then go ahead with rooting .
say me if want any help??
Sent from my Moto G4 Plus using Tapatalk
---------- Post added at 04:16 AM ---------- Previous post was at 04:11 AM ----------
http://cloud.tapatalk.com/s/586730a47ebfa/superuser.zip
on nougat .use this SuperSU file after flashing twrp 3.0.2.0 as before and install phh superuser from playstore
Sent from my Moto G4 Plus using Tapatalk
parth00790 said:
on nougat .use this SuperSU file after flashing twrp 3.0.2.0 as before and install phh superuser from playstore
Click to expand...
Click to collapse
Please, provide complete information, no root method is working on latest (official) Nougat, your half information can brick other's phone and can put them in trouble...
i have used with rooted nougat
just same method for Twrp
enable usb debugging and flash twrp using adb .
then flash superuser.zip provided in previous comment and install phh superuser from playstore .
you are done bro .
i have tried and working
Sent from my Moto G4 Plus using Tapatalk
moto g4 plus brick
can u please tell me where did u get moto g4 plus official stock rom.
and how do u flash into phone.
bro please give me full details :crying:
djsusant said:
can u please tell me where did u get moto g4 plus official stock rom.
and how do u flash into phone.
bro please give me full details :crying:
Click to expand...
Click to collapse
Calm down. Read this.
Wrong, delete please
Ayuda/Help
Hola me podrias ayudar tengo el moto g4 xt1621, lo que sucedio fue que estaba flasheando eol parche de seguridad de 7.0 no recuerdo si era de diciembre o de marzo pero cuando acabo le di en reboot system now pero no prendio mas, solo prende el led y la pc lo reconoce ya instale los drivers pero me da error quisiera saber si me podrias ayudar a fondo a recuperar mi moto g4, disculpa pero lo pongo en ingles y español pero no hablo ingles uso el traductor, ayudame porfavor
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Hello, you could help me I have the moto g4 xt1621, what happened was that it was full of eolo security patch 7.0 I do not remember if the era of December of March but when the reboot system finished now but I did not turn on anymore, just turn on the led And the pc recognizes it and install the drivers but it gives me error I would like to know if you could help me thoroughly to recover my bike g4, I apologize but I put it in English and Spanish but I do not speak English I use the translator, help me please
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
TioHenry said:
Hello, you could help me I have the moto g4 xt1621, what happened was that it was full of eolo security patch 7.0 I do not remember if the era of December of March but when the reboot system finished now but I did not turn on anymore, just turn on the led And the pc recognizes it and install the drivers but it gives me error I would like to know if you could help me thoroughly to recover my bike g4, I apologize but I put it in English and Spanish but I do not speak English I use the translator, help me please
Click to expand...
Click to collapse
Okay -
1)Firstly, what were you doing when you rebooted - were you installing an update? If so, do you remember what the update was (what number did it end in, for example)?
2)Have you tried holding the power button for 2 minutes? This may force a hard reboot and could break your device out of the state it's in.
3)When you plug your device into your computer, what is the device name that comes up (e.g. is it Moto G4 Plus in Device Manager>Portable Devices or Qualcomm HSUSB 9008 or similar)?
4)What error message did you get?
5)Is your device with an unlocked bootloader or locked bootloader?
echo92 said:
Okay -
1)Firstly, what were you doing when you rebooted - were you installing an update? If so, do you remember what the update was (what number did it end in, for example)?
2)Have you tried holding the power button for 2 minutes? This may force a hard reboot and could break your device out of the state it's in.
3)When you plug your device into your computer, what is the device name that comes up (e.g. is it Moto G4 Plus in Device Manager>Portable Devices or Qualcomm HSUSB 9008 or similar)?
4)What error message did you get?
5)Is your device with an unlocked bootloader or locked bootloader?
Click to expand...
Click to collapse
1) I do not remember well
2) I already tried it with volume down and power button plus the charger connected
3) When I connect it to the pc it is recognized by Qualcomm
4) I do not remember, since I have several
5) If you had the bootloader unlocked
TioHenry said:
1) I do not remember well
2) I already tried it with volume down and power button plus the charger connected
3) When I connect it to the pc it is recognized by Qualcomm
4) I do not remember, since I have several
5) If you had the bootloader unlocked
Click to expand...
Click to collapse
Okay, point 3 indicates that you perhaps need to try resetting your phone with a blankflash: you may wish to have a look at this post https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23 Please read all the steps fully before proceeding if you choose to follow that post. I recall you've posted in the hard brick thread too, which has similar instructions, perhaps this may work.
I do not know if this will work, but it's worth a try.
HELP me
Can you give me the link of stock rom for Moto G4 XT1624
This vide will guide you how to root REDMI NOTE 4(SNAPDRAGON)
***IMPORTANT***
BACKUPDATA
Make sure you have adb installed and you place the twrp file to adb folder & other files to internal memory
Downloads:
1. TWRP- 3.0.3-0
https://www.androidfilehost.com/?fid=457095661767136323
2. phh's SuperSu
https://superuser.phh.me/superuser.zip
3. no-verity-opt-encrypt
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip
Steps:
1.unlock bootloader
http://en.miui.com/unlock/
or
Google mi unlock
2.download files
3.enable usb debugging
4.boot to fastboot (volume down+power button)
5.connect to pc run cmd in adb folder .
6.use command (fastboot devices) to check fastboot devices
7.use command (fastboot flash recovery {name of recovery}.img)
8.boot device to recovery (Flash Verity file, su ) ***IMPORTANT***
9.wipe caches
10.reboot
This is not my work all credit to:
XDA:
https://forum.xda-developers.com/re...ecovery-twrp-3-0-3-0-redmi-note-4-sd-t3549970
Video:
https://youtu.be/dV4urAIRKZU
Not working in 8.1.15.0
Unfortunately not working in miui 8.1.15.0.. Eagerly waiting for your response
ashokmor007 said:
This vide will guide you how to root REDMI NOTE 4(SNAPDRAGON)
***IMPORTANT***
BACKUPDATA
Make sure you have adb installed and you place the twrp file to adb folder & other files to internal memory
Downloads:
1. TWRP- 3.0.3-0
https://www.androidfilehost.com/?fid=457095661767136323
2. phh's SuperSu
https://superuser.phh.me/superuser.zip
3. no-verity-opt-encrypt
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip
Steps:
1.unlock bootloader
http://en.miui.com/unlock/
or
Google mi unlock
2.download files
3.enable usb debugging
4.boot to fastboot (volume down+power button)
5.connect to pc run cmd in adb folder .
6.use command (fastboot devices) to check fastboot devices
7.use command (fastboot flash recovery {name of recovery}.img)
8.boot device to recovery (Flash Verity file, su ) ***IMPORTANT***
9.wipe caches
10.reboot
This is not my work all credit to:
XDA:
https://forum.xda-developers.com/re...ecovery-twrp-3-0-3-0-redmi-note-4-sd-t3549970
Video:
https://youtu.be/dV4urAIRKZU
Click to expand...
Click to collapse
twrp titale say its for mtk
amnv said:
Unfortunately not working in miui 8.1.15.0.. Eagerly waiting for your response
Click to expand...
Click to collapse
Wil update you by tmro on the latest version
vikasb32 said:
Not working in 8.1.15.0
Click to expand...
Click to collapse
I did root my device flash custom recovery (TWRP) while running MIUI 8.1.15.0
whats the issue u had? bootloop?
TechRapt said:
I did root my device flash custom recovery (TWRP) while running MIUI 8.1.15.0
whats the issue u had? bootloop?
Click to expand...
Click to collapse
Most of member says this twrp does not work in miui 8.1.15.0, They say after flashing it mi logo flashes for some time and they could not boot into twrp mode
Honestly i haven't flashed it into my device coz most of people facing bugs only in miui 8.1.15.0..
Im miui 8.1.15.0 stable user hope u can help me.
Thank you
Sent from my Redmi Note 4 using Tapatalk
amnv said:
Most of member says this twrp does not work in miui 8.1.15.0, They say after flashing it mi logo flashes for some time and they could not boot into twrp mode
Honestly i haven't flashed it into my device coz most of people facing bugs only in miui 8.1.15.0..
Im miui 8.1.15.0 stable user hope u can help me.
Thank you
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
I am not sure if this is the same TWRP i used
I used the TWRP version from LA 14.1 thread.
I did face few issues though like long boot time but never had issues with loading TWRP or when the OS booted up completely
I am on 7.3.9 build now let me roll back to stable 8.1.15.0 build tonight and re-try the same flash recovery and root method will let u know the results
Not able to boot to recovery
All the installation went as expected till recovery installation. It is done but using Volume Up & Power button not able to go to recovery. Just MI logo post that nothing.
Everything OK but sim slot 2 does not work after root
chandrash3khar said:
All the installation went as expected till recovery installation. It is done but using Volume Up & Power button not able to go to recovery. Just MI logo post that nothing.
Click to expand...
Click to collapse
Rename your recovery as "recover.img".
After flashing recovery don't disconnect the phone
In fastboot type
"fastboot boot recovery.img"
Your phone will boot into recovery
I have redmi note 4 4g 64gb rom 2017 is not unblock.. plz help
:fingers-crossed:
hadiyalkishan said:
twrp titale say its for mtk
Click to expand...
Click to collapse
I have redmi note 4 4g 64gb rom 2017 is not unblock.. plz help
rajendraDMD said:
:fingers-crossed:
I have redmi note 4 4g 64gb rom 2017 is not unblock.. plz help
Click to expand...
Click to collapse
What do you mean?
Not working on my redmi note 4 sd (stable 8.2.10.0). When i try to flash the img file terminal shows lots of help tips. I installed all drivers carefully, still its happening. Please help..
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
kamesh_kraken said:
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
Click to expand...
Click to collapse
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
I was like why didn't I try this before.
You know what happened? The boot process on "Command Prompt" screen went fine. I heard the unplugging the device and replugging the device sound very well. But during all these process it stays on Fastboot mode forever.
I have the latest TWRP loaded for temporary boot process. (3.2.1)
Besides from that
I was finally able to flash with QFIL tool. But still stucks at Lenovo POWERED BY android logo. QCom Downloader didn't work. But QFIL tool did work. I was able to finally come over the "sahara error" by quickly clicking "Download" button after connecting the cable. Then it flashed all the files. Then it finished downloading. But then if I try to switch it on, it wouldn't boot. Still stucks at the screen that I mentioned earlier.
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry!
I tried it with Stock Recovery of A6000 (not plus). It booted into recovery.
Now, I can boot into TWRP. Looks like all the partitions are gone. How do I recover that?
StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
kamesh_kraken said:
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
Click to expand...
Click to collapse
Just flash a new ROM
StillrunsKK said:
Just flash a new ROM
Click to expand...
Click to collapse
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
jameeljb6 said:
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
Click to expand...
Click to collapse
Haha. I know how to do that. Thing is, I can't boot into System or Recovery normally even if I flash via Fastboot. I can only boot to recovery by "fastboot boot recovery.img" Then in TWRP there, I can't flash any roms as it shows Failed to mount /system /data /cache all the time. Tried fixing with "repair file system" option in TWRP. Still doesn't work.
kamesh_kraken said:
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
Click to expand...
Click to collapse
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
StillrunsKK said:
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
Click to expand...
Click to collapse
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
kamesh_kraken said:
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
Click to expand...
Click to collapse
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
StillrunsKK said:
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
Click to expand...
Click to collapse
The TWRP I mentioned 3.1.0 was obtained from RR forum only where dev mentions "F2FS" support. It does show the same error that I mentioned earlier. I did repair, resize, format, change file system. What ever I do, I always get the mount error on 3 partitions. Can't flash any ROMs either. Shows that error 7 and 6. I even deleted the assert line. It would only land me on error 6. I even googled and tried to get rid of that error. But after the error 6 or 7, it shows the same "mount failed".
Not my device. One of my client's. Received as not working.
Hello y'all.
Today I received the update notification and I tried to install it. That's what I got in the attachment. Can anybody give me a light?
sergioricardojsj said:
Hello y'all.
Today I received the update notification and I tried to install it. That's what I got in the attachment. Can anybody give me a light?
Click to expand...
Click to collapse
You need to provide a bit of information about what you have done to your phone. Unlocked bootloader won't matter but any system changes.
kudos1uk said:
You need to provide a bit of information about what you have done to your phone. Unlocked bootloader won't matter but any system changes.
Click to expand...
Click to collapse
I've done nothing. My bootloader is locked. Nothing is changed.
sergioricardojsj said:
I've done nothing. My bootloader is locked. Nothing is changed.
Click to expand...
Click to collapse
Looking at your previous posts that is clearly not the case, good luck.
SOLVED! I flashed the same Stock ROM in the Fastboot Mode and tried to update again, it worked.
sergioricardojsj said:
SOLVED! I flashed the same Stock ROM in the Fastboot Mode and tried to update again, it worked.
Click to expand...
Click to collapse
can you share the rom you flashed please
ccalixtro said:
can you share the rom you flashed please
Click to expand...
Click to collapse
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
sergioricardojsj said:
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
Click to expand...
Click to collapse
thanks but i cant get into fastboot mode only blinking led.
sergioricardojsj said:
This one: https://drive.google.com/file/d/1Eorm8joRrDJnCgJtBR8cqWaHjGbmiFmK/edit
Steps:
Put your phone in fastboot mode
Open command prompt in the downloaded folder and type: "fastboot oem lock" and hold the VOL - for not erasing the data.
Go to the folder again and click in the _Flash_lock.bat - and then you wait until the process to end but be careful, you'll have to press VOL - again for not erasing data after automatic lock.
Boot your phone normally and try to update, good luck.
Click to expand...
Click to collapse
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
barrack1 said:
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
Click to expand...
Click to collapse
Hi, any alternative to solve this issue? I dont think the boot img or partition have been tempered because safetynet check and all my banking apps working fine
i have same problem, i was enable camera2 api for Gcam in my phone, by following tutorial in this forum, Using temporary twrp, unlock bootloader and lock back. And now i cant update with same problem in first post picture. Please someone give us solution for fix this. Thx
Sorry- ignore this message, wrong thread.
ltf_195 said:
Hi, any alternative to solve this issue? I dont think the boot img or partition have been tempered because safetynet check and all my banking apps working fine
Click to expand...
Click to collapse
You don't need to make any modifications, just mounting /system with rw in twrp will break ota.
barrack1 said:
First, the rom is not from an official Xiaomi server. Next, the vol- button trick doesn't actually work since the next time you boot twrp, your user data will be erase. And the update failed on your phone because something on the system partition was changed or you booted into TWRP and set r+w permission.
Click to expand...
Click to collapse
Dude, I'm just trying to help who wants help (I was in need before).
The ROM is not from the Official Website, I took it from a post here I don't remember which post. I'll search and drop it here.
The VOL - trick worked for me.
I never said I booted the TWRP, the phone was in fastboot all the time with .bat command executing the commands.
I'm here for future questions
Hola Sergio Ricardo, no entendí si es oem unlock o local y después los últimos pasos me perdí, podrías explicarlo en español?
sergioricardojsj said:
Dude, I'm just trying to help who wants help (I was in need before).
The ROM is not from the Official Website, I took it from a post here I don't remember which post. I'll search and drop it here.
The VOL - trick worked for me.
I never said I booted the TWRP, the phone was in fastboot all the time with .bat command executing the commands.
I'm here for future questions
Click to expand...
Click to collapse
I was just warning you that the trick as you put it will be nasty one when you or someone else who tries to follow get their phone wiped if they ever boot into twrp.
barrack1 said:
I was just warning you that the trick as you put it will be nasty one when you or someone else who tries to follow get their phone wiped if they ever boot into twrp.
Click to expand...
Click to collapse
He already said he has no TWRP installed and obviously if you're using OTA, you wouldn't have TWRP whilst updating
So does this mean you can't update to january if you have an unlocked bootloader? I had magisk installed in my device, restored image and downloaded the update but it shows installation error. Then after that, I flashed stock pie 9.0 via fastboot from someone who decompiled the payload from OTA and kept bootloader unlocked and tried to update but still it shows as installation error. I have no TWRP installed.
hola,si quieres restaurar la imagen stock para actualizar,as recovery PERO NO EN TWRP y monta la imagen desde ahí, reinicia y listo yo estoy con parche de noviembre que acabo de actualizar y antes de eso tenía magisk con Gcam y mods de audio espero les sirva
Mod edit google translate added:
hello, if you want to restore the stock image to update, as recovery BUT NOT IN TWRP and mount the image from there, restart and ready I am with November patch that I just updated and before that I had magisk with Gcam and audio mods I hope serve them
try n flash original pie fastboot rom from here
http://bigota.d.miui.com/V10.0.4.0....0.PDHMIXM_20190104.0000.00_9.0_2cee840c96.tgz
rexendz said:
He already said he has no TWRP installed and obviously if you're using OTA, you wouldn't have TWRP whilst updating
So does this mean you can't update to january if you have an unlocked bootloader? I had magisk installed in my device, restored image and downloaded the update but it shows installation error. Then after that, I flashed stock pie 9.0 via fastboot from someone who decompiled the payload from OTA and kept bootloader unlocked and tried to update but still it shows as installation error. I have no TWRP installed.
Click to expand...
Click to collapse
Having TWRP installed as the recovery and just booting into TWRP are 2 different things.