running RUU on rooted phone gives me failure to connect thru usb. fastboot oem lock relocked my device and RUU tells me i need to be above 30% to flash, and i'm at 70%
fastboot................unlock token fails
device starts at splash screen with red text and wont continue past
restoring last rom successful, but wont boot past red text
push rom to device fastboot flash zip rom.zip just hangs (i have done this many times in past, it will say failed, too big of file and then ends up working any way.
fastboot oem rebootRUU works, but stil wont flash RUU says battery is dead and it's not
tried usb 2.0 and 3.0 with no luck been running rom that is no longer suported and the updated version that worked best has been deleted from server, so i want to go back to stock. i've tried other roms and was not happy so i just want stock back.
current, relocked boot loader, still have TWRP recovery, s-off, custom firmware, and all that works even though i'm (again) relocked boot loader, and i can't unlock it says faild when trying to flash unlock token
jpwhre said:
running RUU on rooted phone gives me failure to connect thru usb. fastboot oem lock relocked my device and RUU tells me i need to be above 30% to flash, and i'm at 70%
fastboot................unlock token fails
device starts at splash screen with red text and wont continue past
restoring last rom successful, but wont boot past red text
push rom to device fastboot flash zip rom.zip just hangs (i have done this many times in past, it will say failed, too big of file and then ends up working any way.
fastboot oem rebootRUU works, but stil wont flash RUU says battery is dead and it's not
tried usb 2.0 and 3.0 with no luck been running rom that is no longer suported and the updated version that worked best has been deleted from server, so i want to go back to stock. i've tried other roms and was not happy so i just want stock back.
current, relocked boot loader, still have TWRP recovery, s-off, custom firmware, and all that works even though i'm (again) relocked boot loader, and i can't unlock it says faild when trying to flash unlock token
Click to expand...
Click to collapse
Backup all of your data to your PC, HTC Backup or Google, then do a factory reset. Now, try to flash the stock firmware first then the RUU from this site.
majmoz said:
Backup all of your data to your PC, HTC Backup or Google, then do a factory reset. Now, try to flash the stock firmware first then the RUU from this site.
Click to expand...
Click to collapse
i can't, bootloader show locked, and splash screen shows unlocked and it doesn't go past splash screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
all fast boot commands work and when phone was running all adb commands worked, problem is i have a locked bootloader ( image above ) and un unlocked bootloader ( image below ) at same time
jpwhre said:
i can't, bootloader show locked, and splash screen shows unlocked and it doesn't go past splash screen.
all fast boot commands work and when phone was running all adb commands worked, problem is i have a locked bootloader ( image above ) and un unlocked bootloader ( image below ) at same time
Click to expand...
Click to collapse
The splash screen has the warning because you have a custom recovery installed not because the bootloader is unlocked. Try to flash the stock firmware with the instructions in the OP. When it flashes, the red warning will go away. Since you are in the bootloader, try to get to factory reset. It may help clear up some of your issues and allow you flash the RUU.
majmoz said:
The splash screen has the warning because you have a custom recovery installed not because the bootloader is unlocked. Try to flash the stock firmware with the instructions in the OP. When it flashes, the red warning will go away. Since you are in the bootloader, try to get to factory reset. It may help clear up some of your issues and allow you flash the RUU.
Click to expand...
Click to collapse
Nothing, i tried flashing TWRP official instead of modified one i've been running from here, i tried flashing 4.3 firmware, i tried flashing 5 firmware ( on modified version of that from OMJ ) and nothing worked
Final attempt was to bypass the htc driver installer i have and install htc sync. Phone started right up after that. Now to restore to stock ( attempt again )
Related
I have posted a thread about bricking my HTC One a few days ago and actually , I got it finally fixed today with the help of SaHiLzZ!
First of all , thanks man for helping me.
Here's the first thread that I have opened if anyone is interested:
http://forum.xda-developers.com/showthread.php?p=52747826
I was finally able to get past the HTC boot logo and use the phone but I also wanted to update the ROM to KitKat 4.4.
I have changed my CID to HTC__001 from HTC__K18 with no effort , however , I failed to change my MID to PN0710000.
I followed this tutorial step by step (http://forum.xda-developers.com/showthread.php?t=2322820) , but when I applied the fastboot oem writemid command , there was an unknown error and when I rebooted the phone I got the exact same screen as this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now , I'm unable to access anything!!! I can't even get to the bootloader or recovery which was possible with the soft brick. The only 2 screens that I am able to get now is the gray screen as in the picture above , or a complete black screen (and the device still stays on).
I'm unable to use any adb commands , but fastboot commands still work. However , I'm unable to flash any RUU , rom , CWM , TWRP , boot...
Is there's anything I can do about it?
Here's an output of the fastboot getvar all:
Anyone have any idea what can I possibly do to fix this?
You are on eng hboot. And your device is responding in ruu mode. Run the ruu as long as your fastboot is working.
SaHiLzZ said:
You are on eng hboot. And your device is responding in ruu mode. Run the ruu as long as your fastboot is working.
Click to expand...
Click to collapse
I tried it , I used the RUU that fixed the soft brick but it didn't work this time.
It can't get past the bootloader stage because it tries to access the bootloader but with no success.
ciyomh said:
I tried it , I used the RUU that fixed the soft brick but it didn't work this time.
It can't get past the bootloader stage because it tries to access the bootloader but with no success.
Click to expand...
Click to collapse
I didn't understand, is this a continuation of the other thread, or did you get any further? a bit more details please.
nkk71 said:
I didn't understand, is this a continuation of the other thread, or did you get any further? a bit more details please.
Click to expand...
Click to collapse
It got worse but I was finally able to change my MID and fix it. After that I reinstalled RUU 1.29.401.2 (I tried to install anything newer but nothing worked , only this one).
I can use my device regullary now.
I have supercid , mid PN0710000 and JB 4.1.2 on my device.
But the problem now is that I'm unable to update the device using any newer RUU (that match the new mid of my device).
I also don't have superuser or working recovery , when I try to flash recovery , I get this error:
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8758 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
I've tried to flash a few different recoveries but I get this same Unknown error everytime.
How is it possible for me to update from 4.1.2 to 4.4.2/4.4 if I get this same error every time and with no superuser access when every .exe RUU install fails too?
ciyomh said:
It got worse but I was finally able to change my MID and fix it. After that I reinstalled RUU 1.29.401.2 (I tried to install anything newer but nothing worked , only this one).
I can use my device regullary now.
I have supercid , mid PN0710000 and JB 4.1.2 on my device.
But the problem now is that I'm unable to update the device using any newer RUU (that match the new mid of my device).
I also don't have superuser or working recovery , when I try to flash recovery , I get this error:
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (8758 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.011s
I've tried to flash a few different recoveries but I get this same Unknown error everytime.
How is it possible for me to update from 4.1.2 to 4.4.2/4.4 if I get this same error every time and with no superuser access when every .exe RUU install fails too?
Click to expand...
Click to collapse
Can you
1- post an updated "fastboot getvar all" (copy/paste would be better than screenshot),
2- a screenshot of your bootloader screen
3- what recovery are you flashing above? have you checked MD5, cause the filesize looks a bit small,
4- try using a different USB port / PC.
nkk71 said:
Can you
1- post an updated "fastboot getvar all" (copy/paste would be better than screenshot),
2- a screenshot of your bootloader screen
3- what recovery are you flashing above? have you checked MD5, cause the filesize looks a bit small,
4- try using a different USB port / PC.
Click to expand...
Click to collapse
Thank you mate! I tried using a different USB port and it actually worked!
Although I have no idea why should it work but haha it doesn't matter to me.
I have recovery and superuser as well now but I'm still stuck in JB 4.1.2.
I've tried flashing One_4.19.401.11_odexed.zip through recovery and it failed , then I got a mini brick and the phone didn't turn off no matter what I did for a few hours.
Then I see this craziest fix ever , I stuck it in front of a lightbub while holding power + Vol down for about 15 seconds and it worked! lol!
I'm now able to use it , but can't update it in any possible way.
I tried using an .exe RUU of KK4.4 but it didn't work as well (and it was compatible with my mid + cid).
Any idea what can I do to update my device to 4.4.2/4.4 from 4.1.2? I have access now to everything , the android , recovery , supersu , adb ,fastboot..
Thank you!
ciyomh said:
Thank you mate! I tried using a different USB port and it actually worked!
Although I have no idea why should it work but haha it doesn't matter to me.
I have recovery and superuser as well now but I'm still stuck in JB 4.1.2.
I've tried flashing One_4.19.401.11_odexed.zip through recovery and it failed , then I got a mini brick and the phone didn't turn off no matter what I did for a few hours.
Then I see this craziest fix ever , I stuck it in front of a lightbub while holding power + Vol down for about 15 seconds and it worked! lol!
I'm now able to use it , but can't update it in any possible way.
I tried using an .exe RUU of KK4.4 but it didn't work as well (and it was compatible with my mid + cid).
Any idea what can I do to update my device to 4.4.2/4.4 from 4.1.2? I have access now to everything , the android , recovery , supersu , adb ,fastboot..
Thank you!
Click to expand...
Click to collapse
Those 4.4 RUUs are very "sensitive", no idea why sometimes they work, and other times give people a hard time (could be anything OS, antivirus, bad download, USB port, etc)
Why didnt you just take the OTAs to 4.4, before installing custom recovery and root? just reflash the 1.28.401.7 ruu.zip, and take OTAs to 4.4.2 then install custom recovery and root
with S-Off, you can keep bootloader unlocked, no need to relock it or anything; as mentioned in the "Not so FAQ #2" here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Hi friends,
i have a mate s L09 and i had 5.1.1 Lollipop on it CRR-L09C432B161 or something like that.i think it was a rom for Turkey.
i wanted to root it and installed carrera 2.8 twrp with fastboot mode but nothing changed.i could not get twrp.so i could not install supersu and i wanted to install CRR-L09C432B145 rom and my device get bootloop.
So i tried to install other roms via fastboot but nothing changed.
Then i gooogled all the net and did everything but i could't get device back.
i wanted to install twrp rtecovery but i think there is a problem and no rom or recovery got installed.
Now:
1-i don't know which rom was installed on it.CRR-L09C432B161 or something else.
2-i can not install any rom or recovery.(i did many times to extract with Huawei extract tool cust,boot,recovery,system and installed with fastboot but nothing)
3-My device's bootloader is unlocked but i don't know FRP is locked or unlocked(the pic is under)
4-Maybe FRP is locked and i can not install anything becouse of it,i do not know
5-My compuer can't load the device,all the adb drivers installed,no problem.i changed cable and sd card but same problem.
Please help me.i can not use my device.
The pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
]
The Fastboot picture is to small. Can´t read what´s written there but i guess your device is FRP locked since there are two red texts/lines on the bottom side.
The only thing you could try is placing the right Update.App on an SD card and do an forceupdate via Vol+/- and Power. Since you don´t know the original Build, you have to try different files until one works.
Tuerkay said:
The Fastboot picture is to small. Can´t read what´s written there but i guess your device is FRP locked since there are two red texts/lines on the bottom side.
The only thing you could try is placing the right Update.App on an SD card and do an forceupdate via Vol+/- and Power. Since you don´t know the original Build, you have to try different files until one works.
Click to expand...
Click to collapse
Hi,thanks for your reply,
i tried many times that solution.when i do volume+/ and power device get Huawei's erocovery and i press the "update with internet" it says "no wireless found".the other alternatives are "power off" and "reset".
PS:Yes,you're right in the second image,it says:
PHONE Unlocked
FRP Unlock
with red color.
If there is "PHONE Unlocked" and "FRP Unlocked" written on the Fastboot screen, you can flash a new system. Extract System.img Recovery.img boot.img and cust.img from an Update.App and flash via fastboot. To be able to do that, you should search for "Minimal ADB and Fastboot Driver" in the XDA Forum and instal that.
Tuerkay said:
If there is "PHONE Unlocked" and "FRP Unlocked" written on the Fastboot screen, you can flash a new system. Extract System.img Recovery.img boot.img and cust.img from an Update.App and flash via fastboot. To be able to do that, you should search for "Minimal ADB and Fastboot Driver" in the XDA Forum and instal that.
Click to expand...
Click to collapse
ADB drivers all installed.Phone unlocked but it says "FRP Unlock".Not FRP unlocked.i flashed many times new system. Extracted System.img Recovery.img boot.img and cust.img from an Update bu nothing changed.i think they can not installed.
i tried many different roms..B145,B321,B114.And i tried to install twrp recovery but nothing changed again.
i tried all adb command to erase local stroge but isays the command are false.
and i forget to say:my computer can not see the device.it says "device not found".i uninstall the adb drivers and install again the last driver but nothing changed.
Any other way to install rom?
Or if i have to unlock FRP can i install rom?i don't know muck more about the Huawei system.
i upload images again.
You have to use fastboot commands in fastboot Mode. ADB commands wont work. Plug in your Phone. Open device Manager on your pc. Look for "android device". Remove Driver. Unplug Phone. Install "minimal adb and fastboot". Reboot pc. Plug j. Phone. Pc should find Phone now.
Minimal Adb and fastboot drivers also installed.My device shown like this at the device manager.
And i wrote wrong i tries always fastboot commands,sorry.
altanis said:
Minimal Adb and fastboot drivers also installed.My device shown like this at the device manager.
And i wrote wrong i tries always fastboot commands,sorry.
Click to expand...
Click to collapse
contact me, i can solve your problem
mutahharbashir said:
contact me, i can solve your problem
Click to expand...
Click to collapse
Thank you for your reply @mutahharbashir,
but i did not solve the problem and sold my phone.
If i return to Stock with ADB, but not Relock Bootloader, when we received OTA Oreo, can i accept this or brick my phone with bootloader unlocked?
Flash a full stock firmware using fastboot..a matching build as per your software channel
If all partitions are unmodified and stock recovery is installed ( Must for ota installation)..you will be able to install Oreo even if your bootloader is unlocked.. applicable for all type of OTA.
I've successfully received OTA ( Monthly security patch) and installed properly after returning to stock with unlocked bootloader.
Caution : all partitions must be untouched.
No ADB/FASTBOOT on bootloader after OTA update on stock ROM rooted phone
Good evening. I hope you can help me. I'm sorry if I'm posting in the wrong place on the forum. I have already looked everywhere in the www and found nothing to solve my problem.
I have a g5s plus XT1802 rooted. I already tested several roms and was recently at AOSP Extended. Tired of not having dual cam working I decided to reinstall rom stock. I installed and it worked normally until my son decided to do an OTA update. My phone crashed into bootloop straight to recovery. I tried to solve several ways, I got to install other roms via twrp but nothing solved. Finally through the bootloader I decided to use the START function and my device is working again.
After that, every time I reboot the device it goes straight to recovery (TWRP) and I need to enter the bootloader to use the START option.
I tried to reinstall rom stock again using adb / fastboot however after this problem the device is recognized by adb / fastboot devices command only when the cell phone is turned on. When I am in the bootloader it does not recognize. I would like to reinstall the rom stock but without adb it is not possible. Can someone help me?
guguptb said:
Good evening. I hope you can help me. I'm sorry if I'm posting in the wrong place on the forum. I have already looked everywhere in the www and found nothing to solve my problem.
I have a g5s plus XT1802 rooted. I already tested several roms and was recently at AOSP Extended. Tired of not having dual cam working I decided to reinstall rom stock. I installed and it worked normally until my son decided to do an OTA update. My phone crashed into bootloop straight to recovery. I tried to solve several ways, I got to install other roms via twrp but nothing solved. Finally through the bootloader I decided to use the START function and my device is working again.
After that, every time I reboot the device it goes straight to recovery (TWRP) and I need to enter the bootloader to use the START option.
I tried to reinstall rom stock again using adb / fastboot however after this problem the device is recognized by adb / fastboot devices command only when the cell phone is turned on. When I am in the bootloader it does not recognize. I would like to reinstall the rom stock but without adb it is not possible. Can someone help me?
Click to expand...
Click to collapse
pass these commands through fastboot
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
jakson7474 said:
pass these commands through fastboot
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
As soon as I get home today, I'll try this, thank you!
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
joaonds said:
If i return to Stock with ADB, but not Relock Bootloader, when we received OTA Oreo, can i accept this or brick my phone with bootloader unlocked?
Click to expand...
Click to collapse
The problem I'm having is exactly because of this, take care...
So long as you have the stock recovery installed OTA's work fine. My bootloader is unlocked and I'm rooted, but I can receive OTA updates
Same problem
jakson7474 said:
pass these commands through fastboot
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Could not do this.
When my phone is turned on adb recongnize the phone, but fastboot dont and in bootloader either adb and fastboot dont recongnize device.
I have already tried it on a mac and 5 diferent windows computer and same things happens...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
William1020000 said:
So long as you have the stock recovery installed OTA's work fine. My bootloader is unlocked and I'm rooted, but I can receive OTA updates
Click to expand...
Click to collapse
the problem that happend to my phone is because this... after installed a custom rom, and get back to stock rom... OTA update got me to a bootloop... and fastboot dont recgonize my device anymore
Hello, my phone is stuck in Fastboot mode (rebooting does not work, it will always boot into fastboot mode) so I just followed this guide to flash a new ROM: https://c.mi.com/oc/miuidownload/detail?guide=2
But I am wondering, why the installation is still going on after over 10min. - What is wrong?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After trying it again:
It is just stuck forever and I do not know why, I do not get out of fast boot mode and I really do not know what to do now.
Like doesn't the "status" say something what is wrong here? I cannot identefy it, but has anyone enough experience with it and maybe experienced my issue already?
Try flash non-official rom via recovery (twrp). After successful flash, launch system. Then, try flash latest stable via fastboot (do not use FLASH-AND-LOCK, use it only after successfully flashing like flash, check if everything is ok and then flash it again and lock).
I cannot enter recovery, I am stuck in a Fast boot loop. The phone won't let me get into recovery mode.
So flash TWRP in fastboot mode.
And you could try to flash another ROM because "echo Missmatching image and device"
The name of your directory path should not include any space. Replace the spaces with underscores, dashes or just remove them.
From your screenshot, you selected clean all and lock. Try unlocking the bootloader again.
Sent from my MI 9 using Tapatalk
Thanks, but the thing is I fixed all those things already as my last picture shows: https://img.xda-cdn.com/5kNbM-6ZvzA8Jvc_Fc-qUwGIG-Q=/https://i.imgur.com/ZOhtier.png
@Tomcar do you mean 'fastboot flash recovery name.img' ? That does not work, it still boots me into fastboot mode everytime I try to get into recovery mode.
Shure, because you are locked again
I fixed the problem. I just downloaded a newer version of Mi Flash and now I have the newest version installed. So the plan is to install a new custom rom now.
Why is wipe system not recommended to do?
And do I have to "wipe internal storage"?
I really do not understand.. Now as I sad above I have the newest version installed and the phone is unlocked too!
When I go into fastboot mode and do "fastboot flash recovery twrp.img" it works, but when I boot into recovery mode with volume UP and power button the old recovery is still there.
What am I missing out here?
hallohallo222 said:
I really do not understand.. Now as I sad above I have the newest version installed and the phone is unlocked too!
When I go into fastboot mode and do "fastboot flash recovery twrp.img" it works, but when I boot into recovery mode with volume UP and power button the old recovery is still there.
What am I missing out here?
Click to expand...
Click to collapse
Try after "fastboot flash recovery twrp.img"
"fastboot boot recovery twrp.img"
Once you do this, the recovery should stay permanently there.
Dont know why, but this was working for me.
(I hate this phone, too many strange things with it)
On my Mi 9, what I did to make TWRP stick was to press vol up + power right after flashing the recovery, to boot into TWRP.
Sent from my MI 9 using Tapatalk
sangbuana said:
On my Mi 9, what I did to make TWRP stick was to press vol up + power right after flashing the recovery, to boot into TWRP.
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
You my friend are a genius, thanks for the help. That worked!
abocksberger said:
Try after "fastboot flash recovery twrp.img"
"fastboot boot recovery twrp.img"
Once you do this, the recovery should stay permanently there.
Dont know why, but this was working for me.
(I hate this phone, too many strange things with it)
Click to expand...
Click to collapse
Thanks, this did not work somehow the boot command did not get recognized: "C:\Mini ADB and Fastboot>fastboot boot recovery twrp.img
fastboot: error: cannot load 'recovery': No such file or directory"
I was facing the same issue. I stopped the flashing. Copied manually the recovery.img file that came with the flash tool, and flashed the original recovery manually, cause i had it on a customer recovery. Then i tried again, it showed a more meaningful error, basically the path of the folder we're flashing can't have spaces. moved the folder under C: and tried again.. all worked!!
Hello, I've been having this problem for about 2 days, well I'll summarize what happened to save mine and your time.
One day I was working with my g5s plus normally (using pixel experience 9.0), the other day I blocked the phone screen normally, but after that it turned off by itself and it is no longer booting the system...
interestingly it normally goes into bootloader and recovery mode, but whenever I try to install a rom, either custom or stock, it always has the same behavior, I install the rom and start the system, it loads up to the motorola logo and it turns off, it's not like a bootloop, it just loads up to the motorola logo and simply turns off.
I've tried many ways to recover, nothing worked, I tried to pass the rom through rsd lite, through motorola manager and of course through adb, I even tried to install a custom rom through twrp, but that always happens.
recently I was passing his latest rom through fastboot adb, when I noticed that during the process two errors appeared in the terminal, does anyone have any idea what it could be? I will leave the images linked here.
1. at the beginning of the rom installation it displays this highlighted message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. almost at the end of the installation it displays this same message...
I have been there
Flashing wrong stock firmware caused gpt error.
Best way to do that is this.
Install this to your pc and connect your device in fastboot mode.
Sometimes flashing second time with this tool helps.
If it doesn't help, flash firmware of your model firmware (written on back of your phone like XT****) then with rescue flash assistant tool try again to recover in fastboot mode.
If you want to automate and lazy to write use my flash.bat
Finally you achieved to boot the device but no imei or no 4G
1) Unlock oem lock
2) Flash Validus rom
3) Lock oem flash necessary files (You can use my oemlock.bat )
4) Back to stock with rescue and flash assistant.
By the way when rescue and smart assistant finished downloading your model's stock firmware, find where is it and copy it safe place
lynxrz said:
I have been there
Flashing wrong stock firmware caused gpt error.
Best way to do that is this.
Install this to your pc and connect your device in fastboot mode.
Sometimes flashing second time with this tool helps.
If it doesn't help, flash firmware of your model firmware (written on back of your phone like XT****) then with rescue flash assistant tool try again to recover in fastboot mode.
If you want to automate and lazy to write use my flash.bat
Finally you achieved to boot the device but no imei or no 4G
1) Unlock oem lock
2) Flash Validus rom
3) Lock oem flash necessary files (You can use my oemlock.bat )
4) Back to stock with rescue and flash assistant.
By the way when rescue and smart assistant finished downloading your model's stock firmware, find where is it and copy it safe place
Click to expand...
Click to collapse
Hello I've tried in all ways, I tried to restore the soft through RSDLite, from the lenovo software even by the ADB itself, but I wasn't successful, I think the problem is not hardware either.
ocod said:
Hello I've tried in all ways, I tried to restore the soft through RSDLite, from the lenovo software even by the ADB itself, but I wasn't successful, I think the problem is not hardware either.
Click to expand...
Click to collapse
First step:
Try to find gpt compatible firmware and flash it with fastboot.
Not Adb, not Rsdlite, not lenovo rescue asistant only with fastboot!
You will not get 'permission denied' error while flashing correct gpt partition table. If you find this firmware keep it, it could be correct firmware to go next step.
Examine my flash.bat file and don't flash all of them just these
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
I found it my compatible gpt firmware with downloading 30 GB+ stock firmware files then tried to flash every one of them in fastboot mode. Don't give up. I found the solution about a week. I'll check this post daily and try to help you step by step.