Related
Hello community!!
I'm new to the HTC/Incredible S world, I have a rooted/cfw LG P500 and now I bought this great phone. Problem is that I updated it to the last official version before this try.
So I went to the official site and I followed successfully the HTC site steps to unlock the bootloader (golden card?) and now I'm trying to follow the guide
http://forum.xda-developers.com/showthread.php?t=1385084
But I have some problems.
First of all clearly the revolutionary program doesn't work (HBOOT 2.0).
I booted to the bootloader (power+volume down) and I had the error "main version is older" then I copied on the SD card the file for the recovery PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed.zip, I renamed it PG32IMG.zip, it loads it but when I press recovery it gives me an allert icon (the phone with a red triangle + red "!" ) and it does nothing.
I installed the SuperUser app like it is written in the post but when I type SU under the adb shell and it gives me "permission denied".
What could I do?
Is it even possible to downgrade it to a rootable/customable version?
If someone write a guide for rooting with the last update installed from original s-on step to step will be very util and a lot of people will be gratefull!
Inviato dal mio HTC Desire usando Tapatalk
Bootloader unlock and goldcard are 2 seperate things. Bootloader unlock is required at the moment for flashing recovery and superuser for rooting the phone.
Gold card is required for flashing another carriers rom.
Read this thread about recovery http://forum.xda-developers.com/showthread.php?t=1104765
After that you can enter recovery mode and flash a superuser zip file http://goo-inside.me/superuser/
My guide should be able to downgrade your rom and get s-off after that (if after researching you decide you require it) http://forum.xda-developers.com/showthread.php?t=1373697
Hope this helps
Thanks, I'm going to try this as soon as I can, I'll write back the results
edit:
It seems like I can't even pass the first step, the 4EXT Recovery Updater doesn't work, it crushes at EVERY menu item....
(I waited 5+minutes and I had the internet connection on).
I checked and the boot loader says "unlocked". Notice that my device is, of course, NOT rooted (at least for what I know for "rooted", it is still unlocked by the HTC official method)....
you need root to use the recovery updater.
download the recovery image and flash it in fastboot
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
sariel82 said:
Thanks it is finally working!!
I totally forgot that you flash with fastboot via windows console, not within the bootloader....
I hope to finally install something tonight, I'll post some news later.
Thanks again!
edit:
Nothing..I went successfully to the RUU downgrade part but that doesn't work, I tried from the normal system and it blocked because of the hboot version, then I tried within the phone fastboot phase and it blocked again, giving the security failed error...
Click to expand...
Click to collapse
Could I get a couple of screenshots to help with debugging please?
Sure, ASAP
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
edit:
It seems I cannot post the images, too noob ....
Anyway:
I had a photo of the phone in the custom recovery mode, another of the phone with the 4EXT recovery successfully flashing his recovery, another of the script of your post running with this message:
(no errors)
Do you have an unlocked bootloader from htcdev.com (I have)
y OR n:y
<waiting for device>
...
(bootloader) Lock successfully..
FAILED (status read failed (Too many links))
finished. total time: 0.239s
Note: run the RUU in fastboot mode
If all steps etc etc
Now if I try to run RUU NOT in fastboot mode I receive the message:
The Utility of ROM udating can't update the Android device.
Take a valid ROM updating Utility and try again
(I'm translating from Italian)
If I try to go to fastboot after running the script I need to go to hboot using volume down+power since you can go to fastboot only through bootloader and HIS first step is to check the bootloader file (am I right?)
so, since it is again LOCKED the custom boot file I was using PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio_20.2810.30.085AU_3805.06.03.16_M_release_199684_signed
doesn't work anymore and the old one neither so I have to unlock it again and it goes the loop......
So this is the situation, I hope I will be able to post some image soon...
sergiopat said:
Hi!
I have successfully rooted my phone on the last update 2.3.5
The steps I made:
1. Going to htcdev and unlocked the bootloader
2. Flashed a recovery image from clockworkmod.com
3. Installed SuperUser from clockworkmod.com using recovery
I collected the information from a few threads here and had no problem.
I didn't tested custom roms, all I wanted was to root and worked just fine.
I can detail my steps if someone need it.
Click to expand...
Click to collapse
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
sariel82 said:
Thanks, I did too the 3 steps, rooting my device successfully...
But I think I need to do a total S-OFF (deeper than the HTC one) to use the CFWs.
It should be like: follow the above 3 steps and:
4. use some script/console command to prepair the device
5. DOWNGRADE it to 2.2 or something
6. use the "revolutionary" Utility to S-OFF permanently
7. flash the ROMS from the recovery
I cannot pass the 4th step.
Click to expand...
Click to collapse
OK, I thought you only wanted to root.
Thank you anyway
You don't need s-off for CFW's, just the unlocked bootloader. I cannot help you any further until I see screenshots as I'm getting lost in your descriptions. Ctrl prtscrn, paste in paint.
Well, I have the screenshots but I can't post web links in the forum (new user).
Let's see if I can flash some cfw in the mean time
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
sariel82 said:
Now I can post
The phone goes successfully in recovery mode:
http://imageshack.us/photo/my-images/406/img20111215194852.jpg/
Screen of the script with the error:
http://imageshack.us/photo/my-images/41/cmdok.png/
The screen of the phone while RUU got the error:
http://imageshack.us/photo/my-images/440/img20111215195909.jpg/
The RUU screen (translation in the posts above):
http://imageshack.us/photo/my-images/703/catturaruunotok.png/
Btw I tried to flash cyanogenmod, revHD e runnydroid following the instructions (wipe all, super wipe etc), every step was successfull, even the flash part (inistall zip from sdcard), but after the reboot it goes in boot loop (standard white HTC loading screen forever)
Click to expand...
Click to collapse
After you flash a custom ROM in recovery, you have one last step to do to prevent the hang. You extract the boot.img file from the ROM's zip file and then manually flash it in FASTBOOT mode on the phone:
FASTBOOT flash boot [path to boot.img]
That totally solved the problem
Thank you ALL!!!
sariel82 said:
That totally solved the problem
Thank you ALL!!!
Click to expand...
Click to collapse
Hi,
Please list the methods you use from the start. I have also 2.3.5 and hboot 2.0. cant manage to downgrade, i always getting an error.
Thanks
htc developer site -> unlock bootloader
find and download this file:
PG32IMG_Vivo_Gingerbread_S_KT_KR_2.32.1010.1_Radio _20.2810.30.085AU_3805.06.03.16_M_release_199684_s igned.zip
copy it on the sd card and renamto to pg32IMG.zip
reboot in power+volume down mode
go in fastboot
from your pc use fastboot to flash this recovery:
http://forum.xda-developers.com/showthread.php?t=1104765
copy to sd card the superuser file:
http://goo-inside.me/superuser/
enter recovery mode and flash the zip
Then if u want to flash a custom rom you dont need to downgrade, just copy the zip into the sd card, flash it, copy on the sd card the boot.img you find inside the rom zip file and reboot in fastboot (power+volume down)
FASTBOOT flash boot [path to boot.img]
and reboot and the job is done!
Today, I got my new TF701 and as at my TF300T before, I unlocked the bootloader for flash the device.
First I ran through the updates, so that the system is running build 11.4.1.30-20150121.
Unlocking the bootloader was fine but the the flash of ClockworkMod, I ran into trouble.
In first run, everything looks fine but at entering recovery, I saw the dead android.
Then I tried again but all the time, I am getting the same messages
HTML:
fastboot -i 0xb05 flash recovery recovery.img
< waiting for device >
sending 'recovery' (6644 KB)...
FAILED (command write failed (Invalid argument))
Then I tried to erase the recovery for flashing again but the error message was still the same. The connection to the device is fine because
HTML:
fastboot devices
brings the right device information.
The ClockworkMod I tried from the following threads http://forum.xda-developers.com/transformer-tf701/development/rom-t2839030 and http://wiki.cyanogenmod.org/w/Install_CM_for_tf701t
Does anybody has an idea, how to fix and go ahead?
gremly said:
Today, I got my new TF701 and as at my TF300T before, I unlocked the bootloader for flash the device.
First I ran through the updates, so that the system is running build 11.4.1.30-20150121.
Unlocking the bootloader was fine but the the flash of ClockworkMod, I ran into trouble.
In first run, everything looks fine but at entering recovery, I saw the dead android.
Then I tried again but all the time, I am getting the same messages
HTML:
fastboot -i 0xb05 flash recovery recovery.img< waiting for device >sending 'recovery' (6644 KB)...FAILED (command write failed (Invalid argument))
Then I tried to erase the recovery for flashing again but the error message was still the same. The connection to the device is fine because
HTML:
fastboot devices
brings the right device information.
The ClockworkMod I tried from the following threads http://forum.xda-developers.com/transformer-tf701/development/rom-t2839030 and http://wiki.cyanogenmod.org/w/Install_CM_for_tf701t
Does anybody has an idea, how to fix and go ahead?
Click to expand...
Click to collapse
have you tried this one http://droidbasement.com/db-blog/?p=3568 its cwm 6.0.5.1 and its working fine here.
you can also find cm12 unofficials there. its pershoots site
btw im also on 11.4.1.30
tschmid said:
have you tried this one http://droidbasement.com/db-blog/?p=3568 its cwm 6.0.5.1 and its working fine here.
you can also find cm12 unofficials there. its pershoots site
btw im also on 11.4.1.30
Click to expand...
Click to collapse
Oh no, I did not why because I tried before, I had 4 recoveries in use but now, but now it runs fine. Thanks in advance.
PS: I had taken over my PAC-MAN ROM and when it looks fine, I will release.
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
oudric said:
Hello i was using this guide :
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
to root my phone i went and finished fastboot oem unlock step
the problem is after it and booted the phone i extracted the root files and clicked on it
then realized it said oem is not enabled in developer option
so now when i boot the phone a message says"Your Device is Corrupt. It can't be trusted and may not work properly."
and after it like 1-2 sec it turns off
i can still boot in bootloader
PLEASE SOME ONE HELP ME
Also it says device is unlocked in the bootloader statues code 3
extra information i was using android marshmallow 6 latest firmware
Click to expand...
Click to collapse
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
internetpilot said:
The same thing happened to me when I tried to use a rootkit method for rooting the phone when it apparently knew nothing about the most recent updates (MRA58N or MRA58R). I ended up having to manual flash each individual image file from the MRA58N factory image (the flash-all script in the factory image zip wouldn't work). Even so, when I rebooted it still displayed the Your Device is Corrupt message. Then I went through the manual root process again (flashed the modified boot.img through fastboot, then flashed the latest TWRP recovery via fastboot, and then used TWRP to flash the latest SuperSU. Only then did the Your Device is Corrupt message go away and I also had root with everything else working fine.
It definitely made for an un-Godly horrible first 24-hours with my new phone! I hope this helps you.
Click to expand...
Click to collapse
can you please tell me steps i am so afraid to do anything to my phone now and i think my problem is same as yours
i downloaded 6.0.0 (MRA58R) and i used option in toolkit flash stock it gave me an error
"failed (data transfer failure (unknown error))
Its not so easy to brick nexus, but make sure you don't lock bootloader before your phone is working right. You can find the guide how to flash it on XDA.
You will need to flash the missing files by hand.
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
oudric said:
I was able to fix the erro i got by flashing by :
setting up environmental variable
copy all the flash files, all.bat bootloaderXXX.img... etc to platform tools folder
made sure i connected into usb 2.0 port not usb 3.0
then i flashed the stock firmware XD now my phone to point zero again
Click to expand...
Click to collapse
You don't need to move the files to the platform-tools folder.
Go to Nexus 6 General > Sticky rol-up thread > Adb and fastboot. What is it?
This will tell you how to set up and use adb or fastboot properly.
My Asus memo pad 7 is stuck on fastboot.... 123# screen. I've tried temporary recovery and had success installation with lineage-14.1 but nothing changed. Please help. Thanks.
Did you have Lollipop installed before?
Also, do I understand it correctly that you're able to get into the temp recovery session?
Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.
MJMJ7 said:
Yes lollipop was installed and rooted long time ago, after the issue I decided to put it away. I did loads after that though, so I don't think lollipop is still there.
It was first at boot screen, got this fastboot... 123# after I flashed a fastboot image. Flashed loads of recoveries, systems and boot images before and after the fastboot issue.
Hope this helps you understand the state it's in. Thanks for replying.
Click to expand...
Click to collapse
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).
I will try these steps and update you. Thank you very much.
O yes! It worked. Tablet is now back in operation on lineageos. Going and get Gapps now. Thanks a lot lambdadroid
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
lambdadroid said:
If the tablet boots into the screen with the 3 fastboot lines you are in DNX mode, which means you've likely messed up your bootloader. To restore the bootloader, follow the steps outlined in https://forum.xda-developers.com/showpost.php?p=73672837&postcount=5
If everything works, you should get to a second Fastboot screen with NORMAL BOOT etc. From there you can either start the temporary TWRP recovery session (see https://forum.xda-developers.com/showpost.php?p=73673438&postcount=7) to flash the Lollipop package you've downloaded earlier (UL-K013-WW-12.10.1.36-user.zip) or flash LineageOS.
If you want to flash LineageOS you need to unlock your bootloader. Download https://www.androidfilehost.com/?fid=312978532265362065, take the ESP.img from the ZIP and download https://github.com/me176c-dev/devic...recovery-3.1.1-20171119-UNOFFICIAL-me176c.img. Then run:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20171119-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20171119-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD).
Click to expand...
Click to collapse
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
MJMJ7 said:
I believe my work on this tablet is not complete as I can't install Gapps. Installation failing every time. So I tried to reinstall lineage as this was installed before when I was trying all sorts to fix it.
Then when I followed the procedures you sent me, it booted into lineage after I unlocked the bootloader and installed twrp. So the system still had lineage from my fastboot installation attempts. What I can install now is the original version (ul k013 ww-12.10.1.36-user) and that works but I don't want this.
Any help on getting lineage to complete the installation? as it gets to the end with a little to go hut just never finishes (left this overnight)
Thanks.
Click to expand...
Click to collapse
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.
lambdadroid said:
No need to reply twice.
Please clarify: What exactly is failing? The LineageOS ZIP or the OpenGApps ZIP? Do you get an error during installation or does it never finish the boot after installation?
Things you can try: Check TWRP log for errors (usually marked red if you click the bottom right button in TWRP). Try a factory reset in TWRP.
Click to expand...
Click to collapse
Just thought you wouldn't be notified if I don't quote.
The gapps file is giving an error and failing, the lineageOS just stalls and never complete the installation.
I will try again now.....
patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.
Got the Gapps to install, had to choose x86 version. Still no improvement from lineage.
MJMJ7 said:
patching system image unconditionally....
This is going on and on, about 10% left to complete but it never does. LineageOS installation.
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/0-System zips/
Asus Memo pad 7 K013/gapps 7.1.zip'
And that's what I'm getting from the gapps installation.
Installation failed.
Click to expand...
Click to collapse
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?
lambdadroid said:
Maybe the file wasn't downloaded/copied properly. Enable ZIP file signature verification in the TWRP settings and flash the LineageOS package again. Does it print "Zip signature verified successfully"?
Click to expand...
Click to collapse
Did it again with another copy and enabled the verification and all came out successfully. Thanks for your help.:good:
Hi guys. I tried to see other threads but I haven't fint anything. Probably there is but I'm beginner and I don't understand so much Anyway this is the problem:
model LLD-L31
build number LLD-L31 8.0.0.133(C432)
FPR unlocked
bootloader unloced
I tried to install root(Magisk-v16.4) in my device. So I unlocked bootloader, installed TWPR(Pretorian80 2.3.1) successfully but this error "Failed to unmount '/system'(Device or resource busy)" appeared. So I try to format data by recovery hoping that it could be able to read partitions after that. I couldn't yet flash file.Zip so I tried to upgrade Twpr in latest version installing it in recovey ramdisk.
After that I'm not able anymore to get into twpr cause this error appered:
[Func NO : 11 (recovery image) Error NO : 2 (load failed!)
Now, I fortunatly turn on the phone, using it with no problems. I can enter in fastboot and eRecovery. I tried to swipe data/reset but the same error appears.
Can I fix it easily? Tell me if you have any tips, thank you:good:
scugnizz said:
Hi guys. I tried to see other threads but I haven't fint anything. Probably there is but I'm beginner and I don't understand so much Anyway this is the problem:
model LLD-L31
build number LLD-L31 8.0.0.133(C432)
FPR unlocked
bootloader unloced
I tried to install root(Magisk-v16.4) in my device. So I unlocked bootloader, installed TWPR(Pretorian80 2.3.1) successfully but this error "Failed to unmount '/system'(Device or resource busy)" appeared. So I try to format data by recovery hoping that it could be able to read partitions after that. I couldn't yet flash file.Zip so I tried to upgrade Twpr in latest version installing it in recovey ramdisk.
After that I'm not able anymore to get into twpr cause this error appered:
[Func NO : 11 (recovery image) Error NO : 2 (load failed!)
Now, I fortunatly turn on the phone, using it with no problems. I can enter in fastboot and eRecovery. I tried to swipe data/reset but the same error appears.
Can I fix it easily? Tell me if you have any tips, thank you:good:
Click to expand...
Click to collapse
Hi, Not familiar with that Version of TWRP, can you link please?
Failure to unmount system usually means you have system set as "read only", try to change within twrp (when you get a working version flashed).
You say you tried to update TWRP to latest edition, exactly what edition did you flash?
Anyway eRecovery will rescue the phone back to when first turned on.
Sparkrite said:
Hi, Not familiar with that Version of TWRP, can you link please?
Failure to unmount system usually means you have system set as "read only",try to change within twrp (when you get a working version flashed).
You say you tried to update TWRP to latest edition, exactly what edition did you flash?
Anyway eRecovery will rescue the phone back to when first turned on.
Click to expand...
Click to collapse
Hi man thank you for your answer.
I flashed this versionhttps://dl.twrp.me/surnia/twrp-3.2.3-0-surnia.img.html
,try to change within twrp (when you get a working version flashed).
Click to expand...
Click to collapse
I can't enter anymore within TWPR, only in stock recovery.
What made you flash that version, where does it say its for the H9L ?
Try either of these, I use V.01 :-
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
Make sure you use the following command "fastboot flash recovery_ramdisk NAME.img"
When flashed, issue "fastboot reboot" while holding down Vol+, when bootloader page blanks immediately remove USB lead and continue to hold Vol+ until TWRP appears.
TWRP may stall for a while on LOGO page, be patient.
What made you flash that version, where does it say its for the H9L ?
Click to expand...
Click to collapse
I'm dumb man that's all:silly:
Anyway it's fixed now, I love you (thanks put, at least).
Failure to unmount system usually means you have system set as "read only",try to change within twrp
Click to expand...
Click to collapse
Last thing if you can..
On mount section the option mount system partition read-only is disactivated but, at opening, error appears in the same way so I don't know how to disable it definitively
Try formatting Data and then reboot to TWRP (recovery).
Man I'm a disaster:crying:
I formatted but I also had the brilliant idea to delete the whole system, without creating any backup by twpr, obviously. So now I have no OS in my device:good:
I had look for stock firmware with Firmware Finder and I have find one whit these files(bottom photo). Which have I to download?
Then I'll probably follow this thread(https://forum.xda-developers.com/9-lite/help/os-installed-t3787136) to continue. Is it right??
At this stage you are probably better off using eRecovery to bring your phone back to full stock.
From off press and hold Vol Up and connect USB, wait for eRecovery and select "Download latest version and recovery".
Needs WiFi.
savior
scugnizz said:
savior
Click to expand...
Click to collapse
Ah Great, good to hear.
Now, go and flash TWRP and Magisk, but follow the instructions EXACTLY !