Related
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!
I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?
Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.
Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.
Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.
1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.
3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.
Where do I go to get the recovery image?
The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.
Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.
There isn't a link...
Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.
It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.
I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.
I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.
Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back
hey guys,
i have a big problem. i bought a photon q 4g from ebay.
its with sim mod and had a unlocked bootloader (status code: 1)
so i readed some topics about using custom recovery and root for the phone and started
its not the first time i flashed a phone i already had droid2, droid3 and droid4
first i get stuck because fastboot was giving me a message of "variable not supported" & "download size to large"
but i found a mfastboot that flashed the recovery without a error message
so i restart the phone but the recovery not come up.
booting the system is no problem.
but when i wanne go in recovery (power+vol up, from bootloader, adb reboot recovery..) the phone restarts and boot up normal.
Moto boot logo->moto boot logo again->boot animation->system
i tryed to erase recovery and flashed again but the same happen.
tryed with cwm and twrp. maybe someone have the original 3e recovery.img?
and for what is the console option under APfastboot in the boot menu select?
someone know whats the difference between status code 1 & status code 3?
deleting userdata & cache with fastboot only reset the rom i have. :silly:
Status code 3 should be what you need. Maybe you should try unlocking it for yourself to make sure that it actually was unlocked. There are instructions for the full process from unlock to installing recovery to getting root in my signature if you need step-by-step.
Solust said:
Status code 3 should be what you need. Maybe you should try unlocking it for yourself to make sure that it actually was unlocked. There are instructions for the full process from unlock to installing recovery to getting root in my signature if you need step-by-step.
Click to expand...
Click to collapse
that was one of the first things i tryed but it not work. iam not sure what fastboot was saying (i`l look it up when iam at home) something like "no unlock data"
but when i start APfastboot it say "UNLOCKED status code:1" so its not locked.
but cant find information about the difference.
Edit: i see that i have no recovery-from-boot.p. someone know where i can get the correct one?
some more information: the phone run "AP Fastboot Flash Mode (NS) 10.97"
when i typed fastboot getvar all i saw
(bootloader) secure: no
(bootloader) mid: 0000
(bootloader) unlocked: notsupported
(bootloader) iswarrantyvoid: notsupported
the phone is running a not released test firmware with some apps that are not made for public i think.
there is a su in system/xbin and one app named TamperDetect(qualcomm app?)( only 2 button "get var" and "set var") say the phone is permanently rooted
but i installed superuser and it not work.
but other app called DockStatus(moto app?) let me make a adb over wifi with [email protected]_c: #
could that help me fixing my problem?
no one knows what wrong?
huhu1312 said:
no one knows what wrong?
Click to expand...
Click to collapse
I would try giving Motorola a call and see if they can help you. I would think they would at least be able to tell you the difference between the status codes, though who knows if they could get it unlocked for you or not.
no here is no good support in germany
and i read status code 1 = developer device
and why should it be locked if the phone say unlocked?
Why don't you go into the Bootloader menu and try it from this point into the recovery?
VOL_UP+VOL_DOWN+POWER
Loader009 said:
Why don't you go into the Bootloader menu and try it from this point into the recovery?
VOL_UP+VOL_DOWN+POWER
Click to expand...
Click to collapse
if u read my first post correct u will see i tryed and it not work..
Argh, sorry, I only read the first (key-combination) and overread the bootloader and adb.
My Bootloader version is 10.9B.
But my first Line shows "AP Fastboot Flash Mode (S)" instead of (NS).
You should try to contact the american Motorola support...
At least you should try to get some help from them.
I think because you got a developer device, it is slightly different with the partition sizes.
edit: What is with OTA updates on Stock ROM?
i found out S stand for secure NS for non secure
Please try "adb shell" and then "su", do you get a "Permission denied"?
If that works, you should be able to remount the /system partition to rw.
This way you should also be able to install superusers su, somehow... (sorry, never installed it that way)
But this won't help you in your situation.
Please backup your /system, before you make a custom firmware on it (if you'll ever have success).
Those test apps might be interesting.
As you already tried to flash a custom recovery, I assume that the "stock" (or test) recovery is already gone.
My thought is to bring your Bootloader up to date. But I'm not sure, if that would brick your device.
I'm also not sure, if Motorola America will be helpfull with a developer device in your hands.
But without a (valid) sbf flash file you won't be able to flash the appropriate firmware. I haven't seen any official sbf file for our Photon Q.
Theoretically I would say, that you could also try to flash a FXZ file, but it could also brick your device. (Please don't forget to backup /system)
http://forum.xda-developers.com/showthread.php?t=2095536
i know that flashing all can brick the phone thats why i not test it for now.
and yes the root via adb work.
i only found 1 guy in the internet with the same problem like me. he said it was fixed when he flashed a older recovery from GB but is there a old recovery img like this? (this guy had an other phone)
I saw somewhere a stock recovery (that's how I made my OTA Updates).
I still got it, but I prefer to find an uploaded one.
recovery.img 10MiB
CRC32 386A247D
MD5 46CB664521F98B1C1987C288A101A5EC
If you (or I) won't find it, I'll upload it.
Edit: Found it -> http://forum.xda-developers.com/showthread.php?t=2333094
Another one -> http://forum.xda-developers.com/showthread.php?t=1856456
thanks but this files i tryed already;/
i only made a copy of /system/ folder for now
i flashed all with rsd lite 6.1.4 now. and it worked
Hello Guys,
I'm now in deep deep trouble as my Nexus 5 has got soft bricked and now stuck in a bootloop. Yesterday evening i unrooted my device, flashed everything to stock and locked the bootloader back because i was getting a really awful battery life upon rooting. Hence thought of reverting to stock. So flashed the stock image of 4.4.2 and setup my phone just like it came from a factory. Only thing i did this time was disable some Google Apps i.e Play News, Games & Magazines, Movies etc. Till midnight it was working too good with only a marginal battery drain on idle i.e 1% in 2 hrs or so.
Today morning when i woke up, i just entered the PIN code and unlocked the homescreen and then it just got stuck. I restarted my device and since then, its just stuck in a bootloop and whenever the phone tries to restart the OS, its gives numerous errors all related to Play sErvices and something like android.process.acore and Media.
I tried to factory reset by going through the stock recovery but even in that it gives the errors " Failed to mount /cache" and "Failed to mount /cache/recovery" with invalid arguments in the brackets.
Now i can't even flash stock as the Bootloader is in Locked State. I'm able to flash unlock Bootloader but when it asks to restart "fastboot reboot", it again gets stuck on the Google Play services error resulting again in locked state. That leaves me with a LOCKED BOOTLOADER, STOCK RECOVERY & NO USB DEBUGGING ENABLED.
What can i do now to get my device working people ? Feel like :crying: since its happened. Moreover, i can't RMA it as I'm now in a different country from where the phone wasn't purchased.
BBThumbHealer said:
Hello Guys,
I'm now in deep deep trouble as my Nexus 5 has got soft bricked and now stuck in a bootloop. Yesterday evening i unrooted my device, flashed everything to stock and locked the bootloader back because i was getting a really awful battery life upon rooting. Hence thought of reverting to stock. So flashed the stock image of 4.4.2 and setup my phone just like it came from a factory. Only thing i did this time was disable some Google Apps i.e Play News, Games & Magazines, Movies etc. Till midnight it was working too good with only a marginal battery drain on idle i.e 1% in 2 hrs or so.
Today morning when i woke up, i just entered the PIN code and unlocked the homescreen and then it just got stuck. I restarted my device and since then, its just stuck in a bootloop and whenever the phone tries to restart the OS, its gives numerous errors all related to Play sErvices and something like android.process.acore and Media.
I tried to factory reset by going through the stock recovery but even in that it gives the errors " Failed to mount /cache" and "Failed to mount /cache/recovery" with invalid arguments in the brackets.
Now i can't even flash stock as the Bootloader is in Locked State. I'm able to flash unlock Bootloader but when it asks to restart "fastboot reboot", it again gets stuck on the Google Play services error resulting again in locked state. That leaves me with a LOCKED BOOTLOADER, STOCK RECOVERY & NO USB DEBUGGING ENABLED.
What can i do now to get my device working people ? Feel like :crying: since its happened. Moreover, i can't RMA it as I'm now in a different country from where the phone wasn't purchased.
Click to expand...
Click to collapse
I had the same problem.
just download this :
http://liciousroms.com/nexus5_restore.html
and do this instructions :
INSTRUCTIONS::
1) Download and install DRIVERS
2) Download and extract Nexus_5_KOT49H_Restore.zip,
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus_5_KOT49H_Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
2) Download and extract Nexus_5_KOT49H_Restore.zip,
3) Turn on your phone, and connect your phone to the computer (make sure you have USB Debugging enabled on the tablet)
4) Open up folder where you extracted the Nexus_5_KOT49H_Restore.zip
5) Double Click on the "Recovery_Nexus7.bat" and follow the instructions,,,,it really is that easy! (watch video and follow along)
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
^ I can't enable USB debugging as i'm unable to boot into OS.
Guys please HELP ! I'm only looking upto XDA to rescue me out. :crying:
BBThumbHealer said:
Guys please HELP ! I'm only looking upto XDA to rescue me out. :crying:
Click to expand...
Click to collapse
Hi! Check this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833.
Tapatalk-kal küldve az én Nexus 5-el
^ I can't enable USB debugging as i'm unable to boot into OS.
Click to expand...
Click to collapse
Read this:
6) If your phone will not boot and you need to restore, boot your phone into fastboot (volume down and power) and click the "Dead_Nexus5.bat" file found in the folder
Click to expand...
Click to collapse
And try suggested instruction. You don't even need to boot into OS.
Rip95 said:
Read this:
And try suggested instruction. You don't even need to boot into OS.
Click to expand...
Click to collapse
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
Go to the stock recovery and format cache.. Do it a couple of times till the /cache errors go away and then go to the bootloader and flash the stock factory images again. After flashing the stock images, don't boot it up, head over to the stock recovery and perform a factory reset and then reboot!
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Click to expand...
Click to collapse
You can use command in fastboot "fastboot oem unlock" to unlock then reboot in fastboot again, and try this instruction (since you unlocked you should be able to do this).
BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
Here:
bitdomo said:
Hi! Check this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
(BTW you dont have to reboot after bl unlock.
fastboot oem unlock
then flash stock images iwhtout reboot)
What? USB Debugging doesn't have to be enabled. Bootloader unlocking is done from fastboot via 'fastboot oem unlock'.
bitdomo said:
Here:
(BTW you dont have to reboot after bl unlock.
fastboot oem unlock
then flash stock images iwhtout reboot)
Click to expand...
Click to collapse
Bitdomo tried you awesome tool which gave me a slight hope that could revive my Nexus but sadly it didn't :crying: Memory size is matched 32G but userdata erase fails and at last the Download FAIL error is there I just don't know what is preventing the Cache and User Data to erase. Same is the case in Stock Recovery as well.
Can you please get me a solution on this. Would be highly obliged :good:
GldRush98 said:
What? USB Debugging doesn't have to be enabled. Bootloader unlocking is done from fastboot via 'fastboot oem unlock'.
Click to expand...
Click to collapse
BBThumbHealer said:
Bitdomo tried you awesome tool which gave me a slight hope that could revive my Nexus but sadly it didn't :crying: Memory size is matched 32G but userdata erase fails and at last the Download FAIL error is there I just don't know what is preventing the Cache and User Data to erase. Same is the case in Stock Recovery as well.
Can you please get me a solution on this. Would be highly obliged :good:
Click to expand...
Click to collapse
unlock bootloader: fastboot oem unlock DONT restart
download twrp recovery
boot twrp recovery: fastboot boot path_to_twrp_recovery.img
wait until it boots up, if the phone restarts try again.
in wipe settings select format data type yes then ok, if it winished slide the bar to factory reset.
and in cmd terminal type: adb shell then cat /proc/partitions and post the a screenshot about that.
bitdomo said:
unlock bootloader: fastboot oem unlock DONT restart
download twrp recovery
boot twrp recovery: fastboot boot path_to_twrp_recovery.img
wait until it boots up, if the phone restarts try again.
in wipe settings select format data type yes then ok, if it winished slide the bar to factory reset.
and in cmd terminal type: adb shell then cat /proc/partitions and post the a screenshot about that.
Click to expand...
Click to collapse
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
BBThumbHealer said:
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
Click to expand...
Click to collapse
Read the stickies in the general section.. It will tell you how to reset the tamper flag.
- Sent from an IceCold Hammerhead!
BBThumbHealer said:
Successfully unlocked bootloader finally and installed TWRP. Booted in TWRP and performed Data Wipe and it failed. Again unable to mount /cache /persist /data etc commands showed. Then it tried formatting using make_ext4fs function but it failed. Swiped for a factory reset and it failed.
Used your ADB command afterwards and it displayed first daemon started successfully on port 5037 and then error in cmd : device not found.
What next ?
EDIT : Just noticed on the TWRP screen that my internal storage space is being shown as Zero (0) MB Now does this means my flash storage has died ? If that's the case and i need to RMA it, how to relock the bootloader , reset tamper flag and load stock recovery so that google doesn't cause any warranty issues. Please help me in that case as well.
EDIT 2 : Using fastboot, tried flash stock cache.img and userdata.img, it failed. When i flash system.img it went through perfectly. Also, got to know that the steps which you mentioned earlier, TWRP was booted temporarily and bootloader was unlocked temporarily. So does this means i don't need to relock or flash back something ? And, if i've unlocked and relocked the bootloader numerous times, how do i reset tamper flag ?
Click to expand...
Click to collapse
You could try one more thing. Format the /presist partition, For some reason it magically fixed other's devices, like for this guy and for an other in that same thread, but if you format it you will lose your wifi and bluetooth mac address, and some kind of DRM stuff. I made a tutorial how to fix wifi and bluetoot mac address problem after the formating, but I cant tell anything about the drm kind of files, because I still didnt get answers form the guys in that thread. That could mean they are experiencing no problems. Here is the zip which formats persist partition.
BBThumbHealer said:
The tool specifically asks for Unlocked Bootloader and like i've already mentioned, its in a lock state. To unlock that, i need to have USB debugging enabled which i can't enable as i'm not able to even see the lockscreen, just stuck in a bootloop. :crying: I'm able to launch the Fastboot Mode and also partially unlock the bootloader but as soon as i type the command "fastboot reboot", the device again goes into bootloop starting the cycle again
Any more suggestions guys or should i assume my Nexus to be a paperweight ?
Click to expand...
Click to collapse
please quote for me to the next time.
just run "Dead_Nexus" and it's will do all the whole thing though the bootloader...
Aviatar2 said:
please quote for me to the next time.
just run "Dead_Nexus" and it's will do all the whole thing though the bootloader...
Click to expand...
Click to collapse
I tried all sort of things before finally giving up. Ultimately sent the device for RMA. Thanks for your inputs as well
@bitdomo, i have realised it was a case of dead memory chip only. I managed to relock the bootloader and reset the tamper flag (oem device info showed Tamper as "false") but now my only cause of concern is the LG Flash Tool. When i flashed the KOT9H firmware, it changed the original device version as mine came with 4.4 OOTB instead of 4.4.2. Can Google refuse the RMA citing this now ? Rest all, the kernel, recovery, bootloader, tamper flag is all stock. I coudn't even change that back to the original device version as i couldn't transfer any zip to the internal storage as it was dead.
BBThumbHealer said:
I tried all sort of things before finally giving up. Ultimately sent the device for RMA. Thanks for your inputs as well
@bitdomo, i have realised it was a case of dead memory chip only. I managed to relock the bootloader and reset the tamper flag (oem device info showed Tamper as "false") but now my only cause of concern is the LG Flash Tool. When i flashed the KOT9H firmware, it changed the original device version as mine came with 4.4 OOTB instead of 4.4.2. Can Google refuse the RMA citing this now ? Rest all, the kernel, recovery, bootloader, tamper flag is all stock. I coudn't even change that back to the original device version as i couldn't transfer any zip to the internal storage as it was dead.
Click to expand...
Click to collapse
Google can't get your actual device factory version, because it is only visible with lg flashtool, and that tool is an internal lg software. Google has nothing to with that tool.
By the way this lgfalsh tool makes your phone offical, because this is the offical tool used in LG service centres!!!!
Can you imagine a guy at google who takes your phone flashes a custom recovery, reads back the misc partition and search for the factory device version in the hex code. Then he checks your phone serial number and sees 310K then denies your rma request because your device factory version cant be that because in oktober 2013 there were no 4.4.2? I think no.
But if it bothers you then, you can flash krt16m, or if your nexus 5 had to do big update ~150 mb ota update then flash kfs78n if your device is D821 or flash kqs81m if your device is D820. Converted roms work too without problems I have tested them.
bitdomo said:
Google can't get your actual device factory version, because it is only visible with lg flashtool, and that tool is an internal lg software. Google has nothing to with that tool.
By the way this lgfalsh tool makes your phone offical, because this is the offical tool used in LG service centres!!!!
Can you imagine a guy at google who takes your phone flashes a custom recovery, reads back the misc partition and search for the factory device version in the hex code. Then he checks your phone serial number and sees 310K then denies your rma request because your device factory version cant be that because in oktober 2013 there were no 4.4.2? I think no.
But if it bothers you then, you can flash krt16m, or if your nexus 5 had to do big update ~150 mb ota update then flash kfs78n if your device is D821 or flash kqs81m if your device is D820. Converted roms work too without problems I have tested them.
Click to expand...
Click to collapse
I have already sent the defective one for RMA so there's no question of flashing any files now. Google sends the new replacement device and and lieu of that they block temporarily the device's price for a period of 14-21 days in which the service centre ppl check for the issues what got the device in. And i think LG only is handling that as it made the device ? So my question still remains now can the LG guys intimate Google that the phone was flashed. ? But on the positive, the flash tool was of LG and it can't be turned unofficial What say ? I don't wish to pay again for a new device. If the service centre guys gives a thumbs up that phone indeed died as a result of hardware failure like emmc chip, then the card block is removed.
BTW, i am not aware whether Google itself handles the service or asks LG to do the same! Any inputs ?
Hi everyone,
I'm hoping you can help me. I've had a OnePlus One since August 2014, completely stock. Never modded it, never 'flashed' anything, never installed anything outside of the Google Play Store. Always installed the official OTA updates as they pop up on the phone itself. Basically a reeeeealllly boring android user!
So Thursday morning (09/06/2016) I got a notification that a system update was downloaded and ready to install. Clicked install, the process began, phone rebooted as per usual. However, on the install progress screen (the green android with the spinning cogs), about one third of the way through the phone freezes. About 20 seconds later the phone reboots itself and then tries to install the update again. Freezes. Reboots. Tries to install. Freezes. Reboots. Tries to install.... I think you get the idea. It was doing this for a couple of hours before I checked it.
I'm moderately tech-savvy but never really got involved with android modding, rooting or flashing. So I'm a bit confused as to why my completely stock phone is stuck in a bootloop after installing an official CyanogenMod OTA update. The current status of my phone is that I can only boot into Fastboot mode via VolUp + Power. I can get my computer to detect my phone in Fastboot mode, however it informs me that my bootloader is locked. Attempting to boot into recovery mode via VolDown + Power just starts the update install and enters the bootloop.
I've done some research in to flashing a recovery image or manually applying the OTA update. One problem I've noticed is that I have absolutely NO idea what version of Android / CM my device was at before the update, and I have NO idea what version it was trying to update to. I do know that it was some version of Marshmallow before it broke. I've had no issues with the phone before this, aside the occasional self-reboot.
I REALLY want to keep all my data (pictures, contacts etc.) and am very nervous about actually doing anything because I have very little idea as to what I'm really doing.
Can anyone offer any advice on how to get my phone to boot/update/recover through Fastboot with a locked bootloader and without losing any data?
Thanks,
Stormin'
AKA the "HOW DO I PLAY BOOM BEACH NOW?!" guy
Edit: I solved my issue. It might work for you too, permalink to my post (#9) below: http://forum.xda-developers.com/showpost.php?p=67278091&postcount=9
Are you able to get into recovery mode? If so, you should be able to just flash a new ROM. Sideload one using the adb push command, wipe your data (this will clear settings, apps, etc. DO NOT SELECT SD CARD - that will wipe your personal files including your photos). Then install. Hopefully it should all work fine.
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery. Then try the above.
If you can't even get to that stage you're screwed, just like me (unless anyone has any ideas). I've had soft bricks many times before but today I can't even get to the bootloader screen. ADB says the phone is offline. The screen is back and flickers on for a split second every now and then. Bloody CM Updater.
As IBM9001 has said, if you can get into recovery - even being stock - you can still clear your cache - don't do a full factory reset, just the cache, this may help, but even if it doesn't it still rules out one option.
I can't access recovery mode, using the key combo it just boots straight into the installer.
I've got a support ticket open with OnePlus and a scheduled remote assistance tomorrow. However from the preparational email it looks like they are going to factory reset the phone and then clean install CM. They've instructed me to make sure that all my files are backed up... I assume this means I will lose them.
Is there ANY way just to access or pull the photos off my phone? That's the most important bit. Dropbox hit its storage limit at the beginning of 2015 and I refused to pay, so now I have 18 months worth of pictures that I have no other copies of on death row
The only thing I can access is Fastboot...
Edit:
ibm9001 said:
If you can't access the recovery can you access the bootloader sceen (the one with the big green bugdroid)? Then I'd suggest using Fastboot to install a new recovery.
Click to expand...
Click to collapse
I can boot into Fastboot mode, and plugging my phone into my PC works i.e. it is recognised. I have the fastboot .exe and USB drivers, and can issue commands to my phone through cmd such as
Code:
fastboot reboot-bootloader
which works.
How do I use a recovery .img through Fastboot? or can I pull the contents of the sd card through Fastboot?
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Hi guys,
I have the same issue!
If I flash a new recovery from fast boot will I lose my data on sdcard?
Thanks.
Sent from my iPad using Tapatalk
masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I cannot boot into recovery mode, unfortunately
masterjigar said:
Hey mate i had same problem with my friends phone. But in that case i was able to open recovery mode.. So if you can do that just download any full zip of opo.. Like cm12.1 or cm13. Then flash it without clearing data.. So will not loose amything not even a single application..
I did that by using adb sideload just google it how to use it. And for that download full android sdk toollit and then download only fastboot and adb domt download whole studio. Because somete old version of adb and minifastboot will not work on adb sideload... So good luck with that..
Click to expand...
Click to collapse
I'm currently having a very similar issue, but my phone completed the update. It's just stuck in a reboot/"optimizing apps" loop. I can boot into recovery and I tried to clear cache, but It's still just optimizing apps then rebooting and optimizing again over and over. Do you think your suggestion would help me too?
Wooooo, I've fixed it! I don't know why what I did fixed the issue (probably bypassed something) but my phone is up and running again! First thing I'm doing is making a freakin' backup!
So I was just trying everything in desperation. So that others can attempt to fix the same problem, here's what I did:
1. State of phone was either boots normally and crashes when installing update, or boots into fastboot. Would NOT boot into recovery!
2. Booted into fastboot using key combo (hold Volume Up, then Power Button)
3. Attached phone to computer via data usb lead
4. Started up cmd console, used command "fastboot devices" to check that device was recognised (note you need the fastboot files and USB drivers etc., Google it if you're not sure)
5. Used command "fastboot continue" to continue with 'autoboot'. This rebooted my phone but skipped the installer and went to the 'optimising apps' stage. Left phone alone for a couple of hours but it got stuck in another bootloop optimising apps, rebooting, optimising apps and so on.
6. Turned phone off, then booted normally with just the power button. This started the update install again except it didn't crash, and completed the update install. Then it optimised the apps again (albeit with a different total app count) and once finished, phone starts up normally.
Thanks for all the suggestions everyone! Happy to have my phone back. Now to go through the half-dozen or so voicemails I've collected over these last few days... great.
Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.
From the FAQ:
Q4a: Can I flash ROMs or SuperSU or anything else with the stock recovery?
No, the stock recovery can only flash zips that are signed by CM, this means official updates only. You need a custom recovery to flash anything else.
Click to expand...
Click to collapse
Does it mean I can flash an official CM firmware without unlocking the boot loader?
Thanks.
hibernick said:
Hi guys,
@stormin, congrats!
@masterjigar, so you didn't lose the data like photos etc. doing so?
I can boot to recovery, but can't connect by PC to it.
In fast boot mode my PC sees it as well as in dab sideload mode.
I haven't the boot loader unlocked then I have to do it first, right?
But cyanogen site says that unlocking the boot loader will wipe all the device data.
Is there any way get the photos and other files back?
Thanks.
Click to expand...
Click to collapse
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..
Same problem, Also PC not detecting my phone
Hey Guys, I am Stuck at the same thing at Bootloop. But to do anything further I need to connect my phone to the PC. I haven't been able to connect my phone to PC since the time I have got the phone. I tried all available drivers and even tried different cables. I dont know what has been left out to try.
If any one has a working driver pls share the link. Its been three days now that my phone is dead.
Pls help!!
Thanks in advance.
masterjigar said:
That's what adb sideload is all about. It will give you temporary adb access (which is always after unlocking bootloader and root). So you can also flash xip via sideload. Without losing data and media..
Click to expand...
Click to collapse
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks
hibernick said:
can I flash this cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img with the sideload and get adb working over usb?
Thanks
Click to expand...
Click to collapse
You can't adb sideload .img or a partition.
You have to use fastboot.
Code:
fastboot flash boot boot_img_name.img
or
Code:
fastboot boot boot_img_name.img
saurav007 said:
You can't adb sideload .img or a partition. You have to use fastboot.
Click to expand...
Click to collapse
Yes but then I have to unlock my bootloader first. And unlocking bootloader erase all the user files....
Is there other way to to run cm-13.1-ZNH2KAS1KN-bacon-boot-debuggable-b19ebe021f.img on the devise?
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
plee12 said:
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
Click to expand...
Click to collapse
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
aiSanaul said:
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
Click to expand...
Click to collapse
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
plee12 said:
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
Click to expand...
Click to collapse
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
aiSanaul said:
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
Click to expand...
Click to collapse
Thanks very much for your detailed explanations and for your continued support.
Let me answer your question first about why I didn't unlock the bootloader before flashing a custom ROM. Let me backtrack and explain how this problem came about in the first place. My phone was doing an automatic system update two weeks ago (Android 13). After downloading and installing, it tried to boot up. That's when it got stuck in an infinite rebooting loop. At that point, I had no way to change any settings on the phone.
Also, to clear up any confusion, I was not trying to flash a custom ROM. I was simply trying to flash the stock ROM (Android 13), supposedly the same firmware version as the OTA that broke my phone after the automatic system update. I was thinking that perhaps there was an internet glitch during the automatic system update process, which corrupted the OS. So, I was just trying to re-install the same version as the OTA to see if that would solve the problem.
I had also thought about flashing the original version that came with the device (Android 11). But, I think I read somewhere that either Samsung phones do not allow the user to downgrade, or even if it does allow you do so, the downgrading process will wipe out the existing data on the phone. Perhaps you can confirm that or not?
In the meantime, as you suggested, I will look into how to flash TWRP.
Thank you