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
Related
I attempted to root my Wifi only Xoom and I guess something went wrong because I now I have brick with the error msg "Failed image SOS 0x0002" Showing up on the screen.
Here's the story
I installed Android SDK on my Mac and ran the commands following this guide
I got up to Step 10 which is to reboot but it would stay on the Moto logo. I waited around 5 min and did a hard reboot and I waited again for like 10 min. Still a no go.
I was able to get back into fastboot mode and pushed the files again but still won't reboot. I then pushed the system.img and still a no go.
I tried doing the "fastboot oem unlock" a few times to see if that would just help and it didn't change the situation.
So I did a "fastboot oem lock" and not I'm stuck with this brick.
I would appreciate any guidance.
have you tried getting the stock system and boot img files and reflashing them?
Sent from my Xoom using Tapatalk
Sic123 said:
have you tried getting the stock system and boot img files and reflashing them?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
I can't get the computer to see the Xoom anymore. I've trying going into fastboot and even though it says "Starting Fastboot protocol support" I can't seem to issue any commands to the device.
godkillax said:
I can't get the computer to see the Xoom anymore. I've trying going into fastboot and even though it says "Starting Fastboot protocol support" I can't seem to issue any commands to the device.
Click to expand...
Click to collapse
after you oem locked it did you unlock again cause if you didnt thats why it wont do anything in fastboot
you could also take it back and exchange it and say it just wont boot
These kind of storys are why I keep my xoom just the way I got it at the store no rooting for me!. I know someday in a year or so Google and Moto. will give me the updates I need to use the sd card and other stuff. For now I will use my xoom only for checking my E Mail nothing more!
goldsworthy said:
These kind of storys are why I keep my xoom just the way I got it at the store no rooting for me!. I know someday in a year or so Google and Moto. will give me the updates I need to use the sd card and other stuff. For now I will use my xoom only for checking my E Mail nothing more!
Click to expand...
Click to collapse
I think everyone appreciates your opinion on why you haven't rooted yet, but I'm not sure that posting this in the users desperate request for help is the appropriate thing to do.
That being said. To the OP try following what bigrushdog did here to get his to get back into fastboot and to work with ADB and see if this helps. BigRushDog's Thread
try this link follow instuctions and if at leadt prees power and up reboot then press power and volume down get into fastboot i think this will help you it did me good luck but i think you can get it back with this stock image http://www.xoomforums.com/forum/mot...99-how-restore-wifi-only-system-boot-img.html i had to use this to unbrick my tab
im back running 1.3.2 again i tried to backup restore it fomated my internal drive and wouldnt recognize it with clockwork gotta be carefull with new updates some not perfected yet got stuck at boot animations this guide is easy and works great but remember it leaves you in unlocked state with no supperuser active http://www.xoomforums.com/forum/mot...99-how-restore-wifi-only-system-boot-img.html
Thanks for the replies guys. I gave up after I posted since I had an event to attend and since I couldn't power down the device the battery is drained.
I've checked out the post that you guys linked to and my only problem is that the device doesn't show up at all when I do a "adb devices" or "fastboot devices". If I try "fastboot oem unlock" I get a "waiting for device" message.
Maybe it won't allow any debugging if the battery levels are low? I'll leave it charging for a while and if I can't get it to work I've only owned for like 3 days so I'll exchange it.
I had to press vol. up + vol down + power, all at the same time. Then after it lit up with 2 lines of text, (can't rember what it said) I pushed power and vol. up, and it went into fastboot. (wheeew).
I was trying every combination I could think of. Hope it works out for you.
SOS is the recovery partition.. I believe LNX is the boot partition..
this is all according to my gtab nvflash config file.. Why the Xoom wasn't blessed with nvflash is beyond me.
but then again you have a Mac.. I don't think nvflash is available for that ****.
this is taken from my Gtab nvflash config file..
[partition]
name=SOS
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=16777216
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=clockwork.img
Click to expand...
Click to collapse
apparently the wifi xoom has the recov partition as partition 2? I gotta cat /proc/partitions
meow..
ok.. this may be of help
http://forum.xda-developers.com/showpost.php?p=12835567
specifically this post.
http://forum.xda-developers.com/showpost.php?p=12835567&postcount=6
Here's what happens with the following button combo's:
Hold Power+VolUp and release on screen-black: Motorola splash screen(dual core etc) with no text in corner
Hold Power+VolUp until after the splash comes up: splash with "Starting RSD protocol support 3"
Hold Power+VolUp and then hold VolDown immediatedly afterward: Splash screen with "Starting Fastboot protocol support."
Hold Power+VolUp and then VolDown after waiting a second: Splash screen with NvFlash/RSD/Fastboot menu
Hold Power+VolUp and then press VolUp again: Splash with "Starting RSD protocol support 3"
If I choose Fastboot from the menu, it just sits at the "starting fastboot protocol support".
If I choose RSD, it gives me the "starting RSD protocol support 3"
If I choose NvFlash, it says "entering nvFlash (something) and the screen immediately goes black and the notification led comes on (sits there until reboot)
Click to expand...
Click to collapse
This guy talks about the screen going black under nvflash mode.. Its supposed to do that. if you were to plug it in and type lsusb on a nix based computer.. you'd presumably see something regarding Nvidia or APX.. this could provide people with a way to back up the bootloader, partition table, system.img, boot.img, recovery.img and so on.. Not data partition tho..
So the device says it goes into fastboot but it's still not responding to any commands. Just to be through here's what I've tried.
I've tried using my Mac and a windows box both with ADB SDK setup properly. (I have other Android devices that work fine)
I've tried different cables and different ports.
These are the screen I can get the device to boot into.
{
"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 can't get the device to respond to any commands no matter what screen I boot into.
You need to use RSD Lite 4.9 and the wifi dump to get this back. It will tell you it failed to load, but just reboot and youre good to go.
Check my thread in to the general section. I had this same problem on my 3G and you need to use RSD Lite to reload the default image.
Im pretty much in the same boat with no pc recognition. I be tried it all. And even the latest update of RSD 5.0 doesn't recognize it either. Its been a rough past couple of days bow without my wifi xoom. I went ahead and did a repair order form online (really quick and easy) then talked to a rep on the phone and from what he was saying they we're going to send me back a new one or a repair it for free. I was honest with him too about unlocking and then I f'd up by re-locking it. (Failed image LNX 0x0002) so idk we either need a hardware repair or software that could force flash the images
Sent from my DROIDX using Tapatalk
Lnx is boot partition I think. Can you get the device to register anything with your computer when in nvflash mode? That's nvidia's utility. It should at least try searching for drivers, you can get them from nvidias Tegra device section - although I'm not certain if this would be successful for flashing the Xoom as I don't see anything regarding a source for the necessary bct and bootloader files.
The only two modes we can get in are the "RSD mode 2"? and "Starting Fastboot protocol service"
We can't select any other options. I would really love to hear if anyone has been able to recover from this.
Even if its not responding in fastboot try; fastboot oem unlock.
Even if its not responding in fastboot try; fastboot oem unlock.
Click to expand...
Click to collapse
Tried that, it just says waiting for device.
I gave up and returned it. I only had it for 2 days and they took it up with no questions on why it wouldn't boot.
I will attempt to root it again thought.
same thing just happened to me once you reboot it one and get it to say "starting fast boot protocol" you can click root and it will reboot and unlock the device again and at least mine boots back up normally afterwards although its still unlocked so i can't update it to 3.1 -_-
Hello XDA-Developers. Long time lurker, first time poster. After watching the "Noob" video, I feel compelled to apologize in advance for needing to call on your greater experience and knowledge.
The specs (If there's anything left out that you might need, let me know. If I can get to it, I'll post it):
Model: Samsung/Google Nexus S GT-i9020A
Bootloader Ver: I9020XXKA3
Baseband Ver: I9020UCKD1
Carrier: Bootloader says ATT, my actual carrier is Telus.
ROM: Cyanogenmod 7.1 RC1 Experimental
Kernel: Netarchy's Nexus S CFS 1.3.6 Stable
CWM Ver: 3.0.2.4
The problem:
I've been running CM7 for the last couple of months (since I got the phone). I woke my phone, opened the Market, and it suddenly went into a boot loop; not from the beginning Google logo though, just the Nexus S boot screen, and very laggy. I let it try to boot for a while, and did a battery pull when it was (to my apparently idiotic mind) obviously not going to. Put the battery back in and it just sat there on the Google logo for a good half hour.
Here's where things get a little curious. I pulled the battery again, and PWR+VOL UP to get to the bootloader. Load up CWM, and lo and behold, I can't mount the internal SD or the DATA partition. Thus, I can't restore, can't flash anything new, and I've got a phone good for a whole lot of nothing.
What I've done so far:
I've spent the last 9 (yes, nine.) hours searching the internet with increasingly more vague and unrelated search terms. The best solution I've found so far: "Take out the SD card, pull everything off of it and format it. Put it back in to the phone, and presto!" A caveat that you all know: The Nexus S has no removable SD card.
One of the first things I tried, having only fastboot at my disposal, has turned out to be the worst thing I could have possibly done. I tried locking then unlocking the bootloader again, to wipe everything and start from an empty phone. Well, the boot loader won't unlock again. Fastboot sees my Nexus S, fastboot oem unlock yields the familiar "Unlock Bootloader?" screen, and when I select Yes.... Nothing happens. The phone stops responding, the command prompt sits there with "c:\fastboot-path>fastboot oem unlock ..."
Now, the solution to this, according to some, is to wait long enough and do a battery pull to finish unlocking the bootloader. This has yielded no results. Further research indicates that the internal storage may have some kind of hardware problem, a known issue with the Nexus S. Being forced to look at sending the phone in for repairs, I've become a little desperate. I need to removed the CWM somehow. I've got the stock recovery.img, but I'm stuck with a locked bootloader. I did a lot of research into using ODIN to recover the phone back to stock, but I can't get the phone into Download Mode. Using the VOL UP+DOWN then plugging it into USB throws me directly into the screen asking me to unlock my bootloader... except there's no way to say yes or no.
At this point, I'm seriously panicking. This is my only phone, and I'm really quite broke. I can't afford to pay for repairs if they find the phone is out of their ridiculously strict warranty. I can't afford to be without a way to get a hold of me when I'm not standing next to my fiancée or staring at my GMail inbox... Quite literally, my job depends on this phone.
Help me XDA-Developers... You're my only hope.
Update: Odin seems to detect the phone even though it doesn't say download mode, BUT the part of the recovery that writes data fails, and it just hangs. I can't restore using that either, I guess.
Update 2: Forgot to mention, the "Download Mode" screen looks like the unlock bootloader prompt (the green title and the first three paragraphs), and under that it has "USB Control Init//USB Control Init End". When I run Odin, the words "Verify Image (IPBL) ... Success" appear in read above the USB Control Init message. It's at this point it hangs and does nothing for over an hour. After a battery pull, the message "Complete(Write) operation failed." comes up in Odin.
Is there anything I can do here?
sorry im just heading to bed so this is more of a reminder for me to post tomorrow but
what does it say when you try and mount the sd in clockwork? have to tried taking a logcat?
don't panic.
CWM Mount /sdcard returns the error "Error mounting /sdcard!". The same goes for /system and /data.
As far as a logcat goes, fastboot sees the Nexus S, but the ADB shell does not. Sits at "waiting for device" indefinitely if I try at the bootloader. If I try in CWM Recovery, it returns the error: "/shbin/sh: exec: line 1: logcat: not found".
Something must have happened to my /boot partition as well. Doesn't hang at the Google logo anymore, just dumps me back into the bootloader, with a message at the top saying "FASTBOOT MODE - NO BOOT OR RECOVERY IMG". Given that the CWM recovery is still there, I have no idea what's going on with that one.
I am not sure but I think that you are not in the Download Mode. You should see big "Download mode" text on your screen. And you can't boot your phone because you wiped it already with the unlock command therefore the message - no boot no recovery. ADB doesn't work in bootloader.
Question - when you boot into bootloader does it says locked or unlocked? I think that your NAND memory is corrupted, flashing with ODIN could help but you need to see the "Download mode" text in order to flash with ODIN.
My bootloader is currently locked, which is turning out to be a real headache. I can't get the "fastboot oem unlock" command to complete. As I type this, I let the command run for ~15250 seconds (yes, 15 thousand) and did a battery pull, given no indication that it had completed.
Does your Download mode look like this? If yes, that is right. Have you also checked that your Device is recognized from Windows and that the drivers for the download mode are installed?
{
"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"
}
@brainmaster: The drivers seem to be installed properly. "fastboot devices" shows the proper serial. My "Download Mode" does NOT look like that. I'll post a picture as soon as I can. The best way to describe the screen I get when doing the "VOL UP+DOWN" button combination while plugging in the USB is the top half of the screen is the first three paragraphs of the "Unlock Bootloader?" prompt, and the bottom half is the bottom part of the bootloader screen.
It's the only method (other than a 301K resistor on a micro-USB) that I've found to get the Nexus S into download mode. Is there another way?
As an aside, are there different drivers for Download Mode? My phone shows up as "Android 1.0" when using fastboot or the screen that's supposedly "Download Mode", and from when I first rooted the phone, I know it shows up as "Nexus S" when plugged in and actually booted into a ROM. I've applied the Samsung ADB interface drivers to those, and the fastboot works. Obviously I can't check the ADB shell right now.
That is the thing - you are not in the Download mode. If you wore then you will see "Samsung CDMA Modem Device" installed (that is for mine although its GSM device).
And the Download mode should look like that photo with two additional text lines.
I think that its bricked, sorry.
You could pull out battery and let it so for at least 5 minutes, and then try the Download mode - you are doing it right: Vol Down + Vol Up (When the Phone is off) and then plug the USB Cable in the PC.
Thanks for the replies, brainmaster.
Is there a way of completely bricking the phone at this point? I'm trying to figure out a way that the phone will appear to still be under warranty. The only issue is the CWM: if I could get rid of that somehow, then I'd be golden to send this sucker in for repairs.
Only problem is my bootloader's locked.
Don't take 100% for sure, but I think that you already wiped the CWM, since there is no boot image then there is also no recovery.
I still have access to CWM Recovery :|
Have you tried:
fastboot erase recovery
Yes, but the fastboot returns the error that the bootloader is locked and that I should run fastboot oem unlock to run the erase.
Well, all my troubleshooting efforts failed, even the 301k resistor jig. I sent the phone in for repairs on Friday, August 5th. As of today, I learned it's with Samsung's technician right now, and nobody's called about a voided warranty, so here's hoping.
Figured I wouldn't leave the thread at a dead end, in case anyone stumbled onto this from google/xda search:
Samsung sent the repair ticket back to the Telus store with the repair code "REPLACE", so they just gave me a new handset. I have no idea why they just said replace but I have my Nexus back, and that's all that's important.
So are you gonna re-root your Nexus, LOL? Or too much of a headache?
Hah, I rooted and stuck CM7 on it within two hours of knowing the new one I got wasn't busted. Stock just doesn't cut it, potential headaches or not.
Serious Nexus S is serious.
litanyoffail said:
Hah, I rooted and stuck CM7 on it within two hours of knowing the new one I got wasn't busted. Stock just doesn't cut it, potential headaches or not.
Serious Nexus S is serious.
Click to expand...
Click to collapse
LOL!! Yeah, I'm new to the Nexus from HTC Evo 4g and I was on the fence whether to root or not, but I'm gonna take the plunge!! Very unlikely to brick a device except in the most unfortunate of circumstances!
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
This is what I get after running simple oem unlock command via adb
{
"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"
}
Can it be unlocked now?
I was running on 7.0.4.0 Stable - stock out of box, just rooted straight from 3rd party dealer.
Just to update, now I just disconeccted the device from PC and it cant boot. But it worked 4-5 times before, as I was checking bootloader status after few reboots.
PC sees it as QHSUSB_BULK. It's a hardbrick. Any advices?
From what you've done there, nothing should've changed on the device. It was already unlocked, it comes unlocked out of the box.
What else did you do and what do you mean when you say it can't boot? What happens when you hold the power button for a few seconds? Can you still boot into the bootloader (pwr vol -) or the recovery (pwr vol +)?
It's not a hard brick as long as you can still run fastboot, which should work seeing as that's all you've done.
If it's just the PC not recognizing you could try rebooting, clearing adb and device drivers (you can show hidden hardware in the devices management to find your drivers) and reinstalling them.
Logic_ said:
From what you've done there, nothing should've changed on the device. It was already unlocked, it comes unlocked out of the box.
What else did you do and what do you mean when you say it can't boot? What happens when you hold the power button for a few seconds? Can you still boot into the bootloader (pwr vol -) or the recovery (pwr vol +)?
It's not a hard brick as long as you can still run fastboot, which should work seeing as that's all you've done.
If it's just the PC not recognizing you could try rebooting, clearing adb and device drivers (you can show hidden hardware in the devices management to find your drivers) and reinstalling them.
Click to expand...
Click to collapse
UPDATE:
Flashed 7.1.6.0 Stable.
Lost root.
All data and apps present.
Got Chinese apps now.
Google services not working.
It didn't react to whatever I did. Just now I tried holding vol - & power buttons for a minute or two and I got into fastboot. Just reflashed image via miflash and waiting to boot. I see Mi logo and a progress bar loading.
Will report on the outcome.
voolandis said:
It didn't react to whatever I did. Just now I tried holding vol - & power buttons for a minute or two and I got into fastboot. Just reflashed image via miflash and waiting to boot. I see Mi logo and a progress bar loading.
Will report on the outcome.
Click to expand...
Click to collapse
you are doing right but beware 6.xx latest developer rom, it will lock your bootloader and stock recovery again .
voolandis said:
UPDATE:
Flashed 7.1.6.0 Stable.
Lost root.
All data and apps present.
Got Chinese apps now.
Google services not working.
Click to expand...
Click to collapse
Yes, the stable does not have root. You can choose where to go from here, if you want to push the files for root and gapps yourself, or go with a new ROM entirely.
In any case what is most advisable right now is flashing a custom recovery (TWRP) so you have much more control and a bit of extra safety to know that you can more easily recover if you bootloop.
Logic_ said:
Yes, the stable does not have root. You can choose where to go from here, if you want to push the files for root and gapps yourself, or go with a new ROM entirely.
In any case what is most advisable right now is flashing a custom recovery (TWRP) so you have much more control and a bit of extra safety to know that you can more easily recover if you bootloop.
Click to expand...
Click to collapse
Fixed Play Services by complete removal and fresh install from MIUI store.
Is there any way I can actually check if my bootloader is locked or not?
Will flashing TWRP (if BL is locked) lead to brick, or will it simply fail and phone will work?
You checked if your bootloader was unlocked in the first post, that's what
Code:
(bootloader) Device unlocked: true
means.
Only flashing the official dev builds (for now) will lock your bootloader. The version you installed should not have locked it.
A locked bootloader will make flashing TWRP impossible. So just be sure to stay away from those official dev ROM.
Logic_ said:
You checked if your bootloader was unlocked in the first post, that's what
Code:
(bootloader) Device unlocked: true
means.
Only flashing the official dev builds (for now) will lock your bootloader. The version you installed should not have locked it.
A locked bootloader will make flashing TWRP impossible. So just be sure to stay away from those official dev ROM.
Click to expand...
Click to collapse
All good. Flashed TWRP (it's got that no response bug every time it boots), rooted.
Will go for sMIUI now.
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.