Idol 3 Bootloop
I need your assistance
Hi, I have read through all of the posts and tried to find a solution with no luck.
I tend to always go one step too far with my hacking and playing/experimenting.
Alcatel One Touch Idol 3 5.5 6045K
It was booting into TWRP fine.
Then I wrote the non-functioning boot.img (which I thought was the backup of my pre-rooting version) on top of the working twrp recovery image.
So instead of installing the boot.img to the boot partition, I installed it to the recovery partition by mistake.
So now...
My phone just keeps booting and booting.
Alcatel Screen appears
The SuperSU installer starts
runs through its steps
Done!
Cleaning Up....
Will reboot in 10 seconds....
And starts all over again.
adb does not find any devices anymore
I am wondering if it possible at all to format the external sd card so that the phone will boot directly from there.
I have one single ray of hope ( maybe ) . The phone will boot into download mode. (Power off, hole power, volume up and volume down to activate)
The challenge I have now is the USB driver that was working now does not recognize the phone.
I have tried fastboot and I have also tried the OnDemand script. No luck.
I read that the download mode is used for flashing firmware and roms (most likely by the manufacturer)
Has anyone been able to install a rom using the download method successfully?
I am on Windows 10 All-in-One PC
Thanks in advance for any assistance you can provide.
N101BL
More Info
No ideas anyone?
Here is some more info. Hopefully it helps.
So this is what my screen looks like when the phone is turned on. I can only turn it off if it is not plugged in to usb or power.
{
"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"
}
This is the Download Mode. (Power off - then hold power button, volume up, and volume down. Let go when splash screen starts)
Download mode makes a connection sound on my PC so I know something is being recognized.
The phone stops bootloop and waits for something?
This is what appears in Devices and Printers Windows
These are the USB Properties for the USB Driver.
I am thinking that maybe there is a secret usb driver that Telus uses or Alcatel uses to push the firmware or rom onto the phone. Not just the default Alcatel usb driver. (not sure)
Even if I could somehow push a ne SuperSu.zip or my original backup files, everything would be good.
Any ideas would be amazing. I know the trials and tribulations of working with a new product. Hopefully you experts can decode this one.
Thank you.
N101BL (Kevin)
CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.
No Recovery Mode
DallasCZ said:
CAN YOU GO TO RECOVER YMODE? turn off your phone, hold power and volupe up together, release after the phone vibrates...you should go to recovery mode.
Click to expand...
Click to collapse
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)
You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.
what about off warranty repair by alcatel service in your country?
N101BL said:
Sadly no. That would be too easy. I occidentally wrote the not working boot image over top of the working recovery image. (Yes I know, I am an idiot. I knew I was doing it at the time, but I hit reboot anyway. That's when the loop started.)
Click to expand...
Click to collapse
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
petrov.0 said:
You need a bunch of files in order to flash anything while the device is in download mode. Search in baidu for 'tct msm8939 qpst'. You will find info (and the necessary files) for m3g. The device has identical hardware as 6045, but I don't know where the similarities end. Your device can become completely unusable when you play with these tools (QPST, QFIL etc.), but I'm sure that you are aware of this. Good luck.
Click to expand...
Click to collapse
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
famewolf said:
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse
Probably but the files must be released in the wild first. I do searches in baidu from time time in case that something interesting pops up. I also must to admit that the translation of these sites is awful in most cases
Update
Well I sent my phone back.. Fortunately it was under warranty!
But now another hopefully minor issue with the replacement phone.
Please see this thread and post if you know what I am missing. I really appreciate your time and efforts!
http://forum.xda-developers.com/idol-3/help/valid-backup-file-t3199797
famewolf said:
The loop you described doesn't sound like it has anything to do with recovery...you described what happens when you FLASH the boot.img used to root the device instead of just booting it. This will result in the infinate loops. The recovery partition is not used at all until you actually try to go in it by holding down up arrow while it's booting...I would try this several times to ensure you can't get into recovery because if you can get there you can restore your device. If you can not, then it's a paperweight and you should send it off for replacement because it doesn't look like any way to flash it using "download mode" is going to come out anytime soon.
---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------
Perhaps the chinese version of the idol 3 that was just released will lead to access to some of the config files we need.
Click to expand...
Click to collapse
Related
Hey.
So i bought a tf101 and it was never rooted before if you believe the previous owner. I used easyflasher to install, then installed cm10.
So yesterday i was going to bed, open the tablet and boff. Just died.
I could enter the APX mode (i saw it popped up when i connected it to the computer) but nothing else. So since it was late i thought i'l do the unbrick with easyflasher today.
Now i can't even enter APX mode.
So how do i know if it's bricked or hardware issues? Cause i've got ½ year of guarantee left on it.
EDIT: I can now enter APX mode for some reason, tried the unbrick on easyflash. Im using the WW SKU version. The easyflasher seems to have trouble cause the "wheele.exe" get's closed everytime after it uploaded the bootloader to 100%. But the installation still says it's done and no other errors shows up. But still not able to boot anything on the device.
One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?
Lethe6 said:
One way to know if it's "dead" or not is this:
- Power off the device completely (hold the power button for 5 seconds and make sure it's not detected in your computer)
- Make sure ADB is installed (download)
- Run "adb logcat" (without the quotes - see this for more details)
- Boot the device
ADB should say something like "waiting for device..." when you run logcat, and when you boot up you should start seeing the booting process in ADB. If it boots (basically adb will just print stuff forever), then you can probably start suspecting hardware, like the screen for instance. If it stalls during boot, let us know where and what's the error message; it could be corruption somewhere or something alike. If you get nothing at all then I would suspect hardware failure of some sort that's more serious than the screen. If you want to bypass the screen as possible culprit, plug it into HDMI, however you may not get any signal until it's fully booted.
Edit: What's your exact model?
Click to expand...
Click to collapse
This is just wierd. Now it will boot, but only if it's in the charger... When i plug it out it dies. The battery says 76% and haven't moved so the battery seems dead?
And i've got the b50.
This is how it looks when i use easyflasher when it's on APX mode (as it was when i flashed recovery with easyflash). But when i boot up the tablet with charger it's still cw10.
{
"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"
}
Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.
Lethe6 said:
Are you using the APX drivers suggested in the Easy Flasher post? If wheelie closes chances are it's not doing anything to your device at all, which would explain why you still boot CM10. For problems with EF I suggest posting in their thread, I never really had issues so I can't troubleshoot the issue further.
If you're using the drivers maybe there's a hardware related issue, like the internal SD for instance. I've seen some posts here where people have to keep it plugged to USB but I haven't followed them, you can probably find them through a search of this section.
Click to expand...
Click to collapse
I've installed the drivers as wanted by EF. I can browse the internal SD without any problems so i'm not sure about that. Anyway to test that?
I think im gonna download some other rom right to the tablet and try install it. Otherwise i have to go and buy a sd-card thingy for the computer so i can try install stock rom that way i guess.
edIt: Installed Team EOS 4 *JELLYBEAN MR1* but diden't make any diffrence. Now i just need to try get stock and un-root so i can send it to asus :/
So i kinda got it to work out. I think.
I could keep the tablet alive after a while using the keyboard dock after having it being charged for about 10 min. So i had do unistall the "normal" drivers which i could not accsess before and then i worked to make normal rom with easyflash.
But question is:
Is the WW SKU right one for me (im from sweden.)?
Does the recovery go back to orignal also? When i tried to accses recovery all i got was the android green guy who had something wrong with his stomach. Means im back to orginial recovery?
Cause im gonna go back to the store as warranty issue, but i'd like to make it looked as much as possible that it was never rooted or had diffrent roms the the orgiinal.
Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.
Lethe6 said:
Yup the WW firmware is the one for non-US non-Asian and will bring recovery back to stock. You now have a 100% stock device unless you re-rooted it.
Click to expand...
Click to collapse
I downloaded some "check if rooted" app an it says it was not properly rooted which i guess means there is no root existing. Ty for your help man, been awsome. Just hope i won't get charged by asus somehow
Yeah hope so too! Let us know how it ends up going
Worse comes to worse, use PERI http://forum.xda-developers.com/showthread.php?t=1681155
Sent from my Transformer using Tapatalk HD
Lethe6 said:
Yeah hope so too! Let us know how it ends up going
Click to expand...
Click to collapse
So, just wanna update the thread.
The battery was dead so switched it myself after buying one for 50-60 dollars on ebay. Was quite easy, only painful part was putting on the thing around the screen with the power button etc so it would work.
Sweet, glad you got it fixed
Hi everyone,
As many of us know experimenting with stock roms and installing custom roms can lead to many problems, such as boot loops, random restarts, stuck on boot animation etc..
It happened to me, so here is the solution:
1. Power off the device
2. Download the Alcatel Mobile Upgrade app, you can find it on Alcatel site since I can't yet post links
3. Connect your device with USB to your PC while its off.
4. Wait until the battery icon disappears, and then press the both Volume up and Volume down button + Power button.
5. Now the screen will turn red.
6. Open the Mobile Upgrade app and select 6045(5.5) or 6039(4.7) respectivley.
7. Now just click next all the way until the button turns to Download.
8. Long press the volume up button until it vibrates then release.
9. Now press the download button and wait until the process completes.
NOTE: It will take a while since the Alcatel servers are quite slow, in my case it took 3+ hours, but hey it does the job!
Good luck and Cheers!
Hi Thanks for the post, By following those steps can i restore/downgrade my phone firmware to its initial release and remove all the updates ?
because i'm facing some problems and i want to reinstall the system updates properly.
AzizKhb said:
Hi Thanks for the post, By following those steps can i restore/downgrade my phone firmware to its initial release and remove all the updates ?
because i'm facing some problems and i want to reinstall the system updates properly.
Click to expand...
Click to collapse
I think that isn't possible because the software will instal the latest firmware on the device
relvas18 said:
I think that isn't possible because the software will instal the latest firmware on the device
Click to expand...
Click to collapse
Great, so the software will flash the phone and reinstall the firmware on the device ?
AzizKhb said:
Great, so the software will flash the phone and reinstall the firmware on the device ?
Click to expand...
Click to collapse
yes, will install the latest version
AzizKhb said:
Hi Thanks for the post, By following those steps can i restore/downgrade my phone firmware to its initial release and remove all the updates ?
because i'm facing some problems and i want to reinstall the system updates properly.
Click to expand...
Click to collapse
Absolutley, whatever you did or installed this restores the phone to its factory stock rom and settings. Good luck.
relvas18 said:
yes, will install the latest version
Click to expand...
Click to collapse
muderris said:
Absolutley, whatever you did or installed this restores the phone to its factory stock rom and settings. Good luck.
Click to expand...
Click to collapse
That's what i was looking for, i'm going to give it a try.
Great forum with great members, Thanks everyone
AzizKhb said:
That's what i was looking for, i'm going to give it a try.
Great forum with great members, Thanks everyone
Click to expand...
Click to collapse
Sure thing, any time. If you encouter any further issues don't hesitate to ask.
works...
thank you, it is this , I have a dual 6045K yes, and got back to stock ...
very good..
thank you!!!!!
just follow the steps .....
delay and error can give a first time, so back to the beginning
You're most welcome, happy modding.
I don't know if things have changed with Mobile Q, but this sw is janky JUNK.
If I attempt to update while off, it starts when identifying sw version and either craps out connecting to their server or tells me 'there is no greater' i.e. I'm running latest already (which I'm not as OTA is waiting to install). Choose Upgrade anyway after getting phone back off (or download mode) and rinse/repeat. If one didn't turn back off (or download mode), then it would just balk that it can't identify phone (that it just identified to tell me the phone is up to date (which it's not). It's like a mindless loop of step 3. :silly:
Just did chainfire full unroot and wanted to get last update the easiest way.
Maybe it's because phone downloaded latest update OTA, but have as of yet to install (because I didn't want boot loop due to recovery.img
The LGMobile support tool is so much better...
Now that I removed root, how in f-k do I even get back into TWRP.
---------- Post added at 11:42 AM ---------- Previous post was at 10:56 AM ----------
tried again after factory reset, then download mode (funny that's a blank screen after red screen long press vol up). PoS reboots when checking server for latest sw, then
'there is no greater software version available to ugprade your phone,actual version of your phone is the latest.
{
"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"
}
I am waiting on 4.7 in a couple of days.
Trying to get my files together now.
This seems worth having since I love custom ROMs.
Thanks
muderris said:
Hi everyone,
As many of us know experimenting with stock roms and installing custom roms can lead to many problems, such as boot loops, random restarts, stuck on boot animation etc..
It happened to me, so here is the solution:
1. Power off the device
2. Download the Alcatel Mobile Upgrade app, you can find it on Alcatel site since I can't yet post links
3. Connect your device with USB to your PC while its off.
4. Wait until the battery icon disappears, and then press the both Volume up and Volume down button + Power button.
5. Now the screen will turn red.
6. Open the Mobile Upgrade app and select 6045(5.5) or 6039(4.7) respectivley.
7. Now just click next all the way until the button turns to Download.
8. Long press the volume up button until it vibrates then release.
9. Now press the download button and wait until the process completes.
NOTE: It will take a while since the Alcatel servers are quite slow, in my case it took 3+ hours, but hey it does the job!
Good luck and Cheers!
Click to expand...
Click to collapse
Thank you so very much for this.... Alcatel says nothing about booting into Download mode... this did the trick!
Was enjoying the Cyanogen Mod ROM and TWRP, until my phone was blown off a table and cracked the screen just above the USB port... So glad I bought the insurance, but it would have been null and void if still rooted and customized....
Making certain it's completely factory, and slogging up to Cricket tomorrow at 11 to get it replaced, then back to where I originally had this one....
You've saved my butt, and I'm eternally grateful!
(BTW, my PC is running Win10 Pro 64 and the 4.9..2 Mobile Upgrade works like a champ!)
You're welcome, glad it was useful and as always have fun!
anybody know if theres an adb command to get into download mode? im beginning to think my device reboots out of downloade mode when usinf the tool due to faulty power button
carnivalrejectq said:
anybody know if theres an adb command to get into download mode? im beginning to think my device reboots out of downloade mode when usinf the tool due to faulty power button
Click to expand...
Click to collapse
I thinks there is a command for download mode in adb, but only if you had USB debugging enabled previousley.
Thank you!
Thanks bro you saved me 1:40 min under windows 10.1
i love this forum, and i love the work that everyone is doing here!
good luck for you all!!! :victory:
I am currently experiencing book loops during startup of the phone on my alcatel one touch idol 3. Did not want to reset to factory settings, wondering if I can follow the steps to install 6045(5.5) without loosing data on the phone, please help.
Hello
sorry for my question : does this method relock the bootloader too ?
I mean: after install, the phone will be full-stock ?
thanks for answers
rameshidol said:
I am currently experiencing book loops during startup of the phone on my alcatel one touch idol 3. Did not want to reset to factory settings, wondering if I can follow the steps to install 6045(5.5) without loosing data on the phone, please help.
Click to expand...
Click to collapse
If you had USB debugging enabled you could flash the TWRP recovery and create a backup of your data then reset the phone and restore the data.
Hello,
I'd like to say I was told about this site, and I hope someone can help. I find the forum very difficult to navigate.
I have a moto G 2015 that I tried to root, but I fear that I made some mistake or downloaded a bad rom or something because I can only access the root loader, or w/e it's called. The new rom or recovery image or w/e (yes i'm sorry i don't know all the terms) never loaded, and even the backup (which installed successfully) won't load.
Can I factory reset my phone with the original android rom? I really like this phone and it's just a brick now. I'm using my old phone which i don't like as much. I hope someone can help.
You'll have to flash the stock firmware using fastboot, here is the guide. Refer first 2-3 posts by lost101 for the instructions.
Also, the guide has a link for the firmware index where you can download the latest firmware for your particular model (mine is XT1550, for example).
You should already have ADB and fastboot set-up on your PC as you have tried to root. Assuming that you're using Windows, Extract the firmware into the folder where adb.exe and fastboot.exe are located.
Now, boot the phone into bootloader mode by pressing and holding power+volume down button for about 7-10 seconds. You can release the keys once you see an Android robot lying on its back. The screen should read 'fastboot mode'. Connect the phone to your PC, the screen should now day 'USB connected'. Now open a command prompt from the location where you placed the firmware files. You're now ready to flash the stock firmware.
Follow the guide linked above for the required commands. Make sure to do the recovery flash first, factory reset, then reboot to bootloader again to continue rest of the procedure.
BTW, what was the backup you mentioned that restored successfully? Can you describe it more?
Broadcasted from Zeta Reticuli
Let me provide some images I took with my other phone. It might help.
OK I have osprey xt1540 and i used something called Team Win Recovery Project v2.8.7.0. I can still get into the TWRP thing, and there's a bunch of options i'm sure you're aware of. The backup of my phone that I made doesn't seem to work. It will load say that it loaded properly. Maybe I can provide some photos to show you what I've done.
The backup was simply a backup of my phone before attempting to flash it the first time. It was meant as a way to recover the phone I think..
edit: OK so I'm not allowed to post pictures because I have fewer than 10 posts. That's going to make it harder to get help.
edit 2: BTW In the list for stock firmware I'm not sure which one to take. I found the version of my phone, but it seems newer than any of those listed. 24.71.2 where the newest there is 24.65.33 ?
I found a more recent firmware, but it still doesn't exactly match my phone (I think?) I'll post them
My phone: 24.72.2.osprey_retca.retca.en.ca
Most recent found: MotoG3_XT1540_OSPREY_RETCA_5.1.1_LPI23.72-16.3_cid14_subsidy-DEFAULT_CFC.xml.zip
And I found it from this thread: https://forum.xda-developers.com/showthread.php?t=2537119
Also I wonder if my phone will work if I can just relock the bootloader somehow. I get stuck on that screen that warns about the bootloader unlocked (white screen with motorola warning.) I can get on that screen, the bootloader, and then the team win recovery thing. I hope this helps
First I would suggest you flash a much more recent version of TWRP.
https://forum.xda-developers.com/devdb/project/dl/?id=25599
Instructions are in OP here:
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Then try to restore that backup again.
Don't forget to wipe before you restore.
KrisM22 said:
First I would suggest you flash a much more recent version of TWRP.
https://forum.xda-developers.com/devdb/project/dl/?id=25599
Instructions are in OP here:
https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Then try to restore that backup again.
Don't forget to wipe before you restore.
Click to expand...
Click to collapse
Thank you for this. Using the codes in that help I can't seem to do anything. I just get errors, or nothing at all.
mobile.frank said:
Thank you for this. Using the codes in that help I can't seem to do anything. I just get errors, or nothing at all.
Click to expand...
Click to collapse
I would need to see a copy of your terminal output.
Try what you were doing again in TWRP, this time after the error, use the third button on nav bar (right to the home button, 4 horizontal lines) to switch to terminal output window; then press and hold down power+volume down to take a screenshot and then upload it here, it might help us understand the situation better.
And if you are aiming for a stock firmware install, probably 'XT1540_OSPREY_RETCA_6.0_MPI24.65-33.1-2-2_cid14' is what you want. Got from the firmware index thread here.
BTW, you can try some threads on the off-topic section to increase your post count.
Broadcasted from Zeta Reticuli
KrisM22 said:
I would need to see a copy of your terminal output.
Click to expand...
Click to collapse
OK i'm going to post some screenshots, but I don't think I can post here so I will try to provide links.
I connect my phone to computer and stay on this screen to use fastboot (I realise it says connect usb cable. I always connect my phone to computer and it does recognize the device "USB connected" before attempting anything.) I imagine i have to update the TWRP from this screen, but the instructions in the links you sent me don't correspond with the files that I downloaded. If I type in what I downloaded it doesn't work.
{
"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"
}
This is the program and screen and instructions. The codes there don't work because the filenames are different:
This is an example trying to use the recovery img which tbh I'm not even sure what image that is.
I attempted to root my motorola a long time ago, that's why i can't remember how i managed to do any of it. I think I deleted all the links to the instructions I was using.
mobile.frank said:
OK i'm going to post some screenshots, but I don't think I can post here so I will try to provide links.
I connect my phone to computer and stay on this screen to use fastboot (I realise it says connect usb cable. I always connect my phone to computer and it does recognize the device "USB connected" before attempting anything)
This is the program and screen and instructions. The codes there don't work because the filenames are different:
Click to expand...
Click to collapse
fastboot devices shows the devices that are in fastboot mode (same as bootloader mode in our case) connected to the PC. So, connect the phone via USB and try running that command, it'll show up your device's serial no. and 'fastboot' written on the right side.
Now, rename your recovery image to twrp.img. Or you n modify the command itself. Make sure that the recovery is in the same folder as these 4 files. For example, if your recovery is named twrp-3.1.0.0-osprey.img, then type in-
Code:
fastboot flash recovery twrp-3.1.0.0-osprey.img
after you get a [DONE], scroll down and select recovery in phone.
If you already have a twrp version installed now, then copy the new twrp.img file to your sdcard. In TWRP>Install>install image. Select the file, select recovery in next step and swipe to flash.
Broadcasted from Zeta Reticuli
from the lying down android in the first picture, it shows you have stock recovery.
KrisM22 said:
from the lying down android in the first picture, it shows you have stock recovery.
Click to expand...
Click to collapse
That's the bootloader screen, not recovery.
Sent from my MotoG3 using Tapatalk
OK I managed to update the TWRP and am trying to restore the phone backup from the SD card. I made the backup before making any changes when I tried to root my phone.
I don't know if anything works because every time the phone reboots I get the "Warning bootloader unlocked" screen; so maybe it even worked when i tried to root it, but is just always stuck on this screen. I only get that screen, or the bootloader screen if I go to it.
OK so I tried to follow these directions with the factory image for my phone, and it didn't work. I get a nice motorola boot screen, and then nothing:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images#
I strongly suggest you look at this:
https://forum.xda-developers.com/20...gin-how-to-t3599251/post72111431#post72111431
That will also tell you how to get rid of the nasty bootloader screen.
Also make sure you WIPE dalvik/art,data,system,cache before you restore. Anything.
I got the phone yesterday, I rooted and today I tried to disable fused location, but when I did it and reboot, it shows me a screen, not bootloop, only a screen with asian characters which I don't understand except 'rf' in the middle.
{
"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"
}
So what I can do? I treated like a hard brick? I tried downloading the package-restrictions.xml file and change from disable to enable but that didn't work.
I was thinking than maybe installing the system from 0 could help but I suppose the zips from here don't work since it doesn't rewrite the data partition, and most probably the fail is there no?
EDIT: More information, seems the error is about an RF test https://forum.xda-developers.com/oneplus-x/help/stuck-rf-test-boot-t3610400
If you have an unlocked bootloader use this to restore to stock. This has saved my phone once.
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
set92 said:
I got the phone yesterday, I rooted and today I tried to disable fused location, but when I did it and reboot, it shows me a screen, not bootloop, only a screen with asian characters which I don't understand except 'rf' in the middle.
So what I can do? I treated like a hard brick? I tried downloading the package-restrictions.xml file and change from disable to enable but that didn't work.
I was thinking than maybe installing the system from 0 could help but I suppose the zips from here don't work since it doesn't rewrite the data partition, and most probably the fail is there no?
EDIT: More information, seems the error is about an RF test https://forum.xda-developers.com/oneplus-x/help/stuck-rf-test-boot-t3610400
Click to expand...
Click to collapse
If post above does not work use the msmtool
I tried the method of miket674, first with "flash-all-partitions-fastboot" and then with "flash-all-partitions" without luck.
I'm trying with your method now, but the part of USB_BULK is not working, or nothing appears or a Oneplus without drivers recognized appear in device manager.
EDIT: I followed the guide, but it showed me an error of sahara communication failed, so I unplug, I tried to power on, but now it don't listen to the power on button.....
EDIT2: Seems now it can wake up or do anything at all, so the guide for fixing hard brick, let the phone worse than hard brick xD I contacted with oneplus support and they told me they need to perform an Inspection but maybe they fix the phone like it were in warranty.
EDIT3: After pressing power on + vol down like 10s or more it boot up to the error from before.
EDIT4: At the end I finished to do all the steps of MsmDownloadTool V4.0 but nothing, he finished, auto booted and the same chinese words with rf in the middle.
EDIT5: Weirdest thing happened, I went to sleep, and 3h later I tried to turn it on and the error was not there, and it welcome me with a clean OOS.... so not sure what fixed it, if the first method or the second, but seems fixed...
EDIT6: Aaaand the error came back when I rebooted because the step of "Adding finishing touches" never ended.
in TWRP
/data/system/users/0/ rename package restriction to .old
this resets your apps that have been disabled to enable incase you break something disabling apps in TIBU
---------- Post added at 02:49 PM ---------- Previous post was at 02:48 PM ----------
why dont you format /data in recovery?
After EDIT6 I tried to format /data from recovery but didn't work, also i think the first method already wipe all the partitions. And I can't access TWRP because now the recovery is the standard one
EDIT: Seems that if I wait more than 10 minutes with the phone turn off and then I boot it, then it goes to a clean OOS, although is the second time getting stuck in "Adding finishing touches", and this time instead of reboot it, I'm going to let it until it wants to end.
EDIT2: 30 minutes later the phone finished with the "Adding finishing touches", so now I'm updating to OOS 5.1.9 and I'll try to reboot it, but I think it will happen as before and it will show me the error, it may possible be happening this because of the 2 partitions? Maybe when I wait 10 minutes to start it boot the other partition which don't have the error.
YOU NEED TO DOWNLOAD MSM TOOL FOR ONEPLUS 6 GO TO QUALCOMM MOD BY PRESSING VOL DOWN + POWER BUTTON DOWNLOAD QUALCOMM TOOL ON
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
set92 said:
I tried the method of miket674, first with "flash-all-partitions-fastboot" and then with "flash-all-partitions" without luck.
I'm trying with your method now, but the part of USB_BULK is not working, or nothing appears or a Oneplus without drivers recognized appear in device manager.
EDIT: I followed the guide, but it showed me an error of sahara communication failed, so I unplug, I tried to power on, but now it don't listen to the power on button.....
EDIT2: Seems now it can wake up or do anything at all, so the guide for fixing hard brick, let the phone worse than hard brick xD I contacted with oneplus support and they told me they need to perform an Inspection but maybe they fix the phone like it were in warranty.
EDIT3: After pressing power on + vol down like 10s or more it boot up to the error from before.
EDIT4: At the end I finished to do all the steps of MsmDownloadTool V4.0 but nothing, he finished, auto booted and the same chinese words with rf in the middle.
EDIT5: Weirdest thing happened, I went to sleep, and 3h later I tried to turn it on and the error was not there, and it welcome me with a clean OOS.... so not sure what fixed it, if the first method or the second, but seems fixed...
EDIT6: Aaaand the error came back when I rebooted because the step of "Adding finishing touches" never ended.
Click to expand...
Click to collapse
It is more than likely a hardware issues then if it came back for no reason at all, I would send to oneplus
Just try to lock the bootloader back which will make your device normal as it came from box then you can unlock it again
I'm having so much trouble with this process, I think at least in part because it's a no-name brand with no manufacturer website for resources, but also most guides I'm finding on the rooting process are very much "draw the rest of the owl". Lots of "okay now do this with this file" without explaining how to do that or where to get the file, which leads me to my current problem. I'm trying to follow the guide here. Where I'm stuck is "GPT file from your firmware or backup". No idea how to obtain that. I have the firehose programmer file, I think; the main guide I'm following to try and root my phone, here, says I need prog_emmc_ufs_firehose_Sdm660_ddr.elf, which I've downloaded. I have all the drivers, I have QFiL, I have QPST, I have Qualcomm GPTtool, and I don't really understand what to do with any of them or why it's not working. What I need, based on the main guide I'm using, is rawprogram0.xml and patch0.xml. But I need the GPT file to generate those? I'm so far over my head with this, I just want my phone rooted and working. Also, tried the secondary method at the bottom of the main guide (second link), and got this result:
{
"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"
}
Edit, because apparently XDA is all about posterity and doesn't like threads on completely different problems if they're the same person and the same phone: I did finally get to the point of rooting it. The major problem I have now is that it will only boot to fastboot mode. I can get it into recovery mode, but I get the dead android with "no connection" under it, and I've tried everything the internet has suggested to get past that, and it won't. Additionally, any fastboot command (apart from "fastboot devices") I try in ADB returns "FAILED (remote: 'unknown command'). I don't know how to get it into EDL mode from fastboot. I've tried every button combo possible, and the only one that does anything different is power + volume up, which changes it to a bright white screen. At this point I just want to do a hard reset so I can take another go at the rooting process, but the phone doesn't seem to want to allow me to. I would appreciate any help with this; I don't have a working phone at the moment because of these issues.
use linux, no rawprogram0.xml needed (you can however generate rawprogram0.xml with this)
https://github.com/bkerler/edl
I don't have Linux, I don't want Linux, but that link might be useful if I reach the point where I can try rooting again. So far out of six places, no one has been able to help yet.
QFIL is a pain. linux is easier when it comes to usb connection, no need to worry about drivers.
the link itself contain bootable iso you could run from pendrive. however it's possible to install python and run everything on windows, too.
for EDL mode try these methods
- power off device, hold both Volume keys and plug in usb-cable
or
- fastboot oem reboot-edl
or
- DIY deep flash cable
or
- test point method
once in EDL mode you can flash little kernel which contains fastboot instruction set, brings fastboot back to life.
with that EDL tool one can enable OEM unlock, then unlock bootloader from fastboot. once unlocked, flash phhusson's or AndyYan's GSI or whatever ROM and U683CL firmware from one of the U683CL threads.
it's good you already have working firehose loader for this device, device can be unbricked and rooted easy.
In looking up how I might find the test points for this phone, I found a video on factory resetting this exact model, which contained the revelation that to get past the "no connection" android, I needed to hold the power button and TAP volume up once, rather than hold it like I've tried before. So I got into recovery mode, but I wiped the data and the cache and it's still only booting into fastboot. If I hold the two volume buttons and then plug it into the computer, I get the white screen, so maybe that's EDL mode as the phone stands right now? QPST's detecting it now, at least, as Q/QCP-XXX (Sahara Download). So I guess I'll try reflashing. I think I still have the stock firmware somewhere, but do I need a ROM as well?
I have/had this device, I was able to root no issues. It's a junk device and I quickly quit working on it but I think I posted stuff for it on here at one point
somnomania said:
In looking up how I might find the test points for this phone, I found a video on factory resetting this exact model, which contained the revelation that to get past the "no connection" android, I needed to hold the power button and TAP volume up once, rather than hold it like I've tried before. So I got into recovery mode, but I wiped the data and the cache and it's still only booting into fastboot. If I hold the two volume buttons and then plug it into the computer, I get the white screen, so maybe that's EDL mode as the phone stands right now? QPST's detecting it now, at least, as Q/QCP-XXX (Sahara Download). So I guess I'll try reflashing. I think I still have the stock firmware somewhere, but do I need a ROM as well?
Click to expand...
Click to collapse
stock firmware is the rom
for QPST/QFIL you need rawprogram0.xml and Qualcomm HS-USB QDLoader 9008 Drivers.
with ROM i mean android boot + system partition (+ vendor maybe).
with firmware I mean bootloader, tee, baseband, modem, sim, wifi, touch, sound, etc (various partitions).
the former one can be replaced with custom ROM or GSI, or just use stock ROM. the latter is important for unbricking. usually it's all together bundled in full stock ROM/firmware download.
PizzaG said:
stock firmware is the rom
Click to expand...
Click to collapse
Thank you.
I have all of that, and I'm still having issues. With QFIL, I'm getting Sahara fail, process fail, and flash information is not filled. Now I can't even get it to detect the phone, after multiple attempts and disconnecting and reconnecting and closing QFIL and reopening it and moving files, it's like it got tired or something. And I attempted the GitHub thing, but I'm stuck on installing because CMD tells me when I put in "pip3 install -r requirements.txt" that "pip3" isn't recognized as anything. I think that method is too much for me anyway, I don't understand most of what it says past the installation part.
I don't know about windows but try pip.exe and pip3.exe
Code:
%USERPROFILE%\AppData\Local\Programs\Python\Python39\Scripts\pip.exe install -r path\to\requirements.txt
usage is quite simple, but you need to connect device in EDL mode before a certain timeout. try with battery removed and both volume keys. linux no need for drivers or rawprogram0.xml
this is how I read recovery partition off device (on linux)
Code:
python edl r recovery recovery.img
Spoiler: example
Code:
[email protected]:/media/xubuntu/18CC6C07CC6BDE0E/src/edl$ python3 edl.py --loader='/media/xubuntu/18CC6C07CC6BDE0E/Android/Backup/citrus/POCO M3 - Redmi 9T nfc - Redmi 9 Power - Redmi note 9 4G/prog_firehose_ddr.elf' --memory=UFS r recovery recovery.img