Related
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,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Sounds like you might have encrypted it?
BobbaLouie said:
Sounds like you might have encrypted it?
Click to expand...
Click to collapse
Not consciously, the phone had normal use....
If it was encrypted you'd have to enter a password before it even got to the boot logo, so it would be very obvious.
BobbaLouie said:
If it was encrypted you'd have to enter a password before it even got to the boot logo, so it would be very obvious.
Click to expand...
Click to collapse
Then, it is not encrypted.
thanks
Jorge BCN said:
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Click to expand...
Click to collapse
Are you rooted? If so, you might have to FORMAT your phone, which will erase even your storage. I used TWRP and my phone just factory reset after I formatted. I think there must've been some sort of corruption.
Jorge BCN said:
Hi,
My phone started to fail and give me a lot of errors that it was stopping initiator, android.process.acore, etc... and got stuck in this errors, having to accept the error dialogs all the time and being impossible to make anything with it.
I tried to reset my moto G and wipe all user data. I entered fastboot mode (couldn't do it form phone normal menu) and made a factory reset. No changes after reboot.
Then I tried to reinstall firmware. I've made all the steps in several tutorials found here. The bootloader is unlocked, I put the last firmware , entered recovery mode and ask for wipe/reset user data, but when the phone reboots, there are no changes: I have again the personalized screen image and the gesture blocking, as if the user data remains there, and all the errors.
Is there any way to erase all user data and leave the phone as the first day? Am I making something wrong or need to make something more?
Thanks in advance
Click to expand...
Click to collapse
Try clearing data,cache,dalvik cache and reflashing the ROM..if all fails try to clear data and flash the stock ROM through fastboot mode.
KVCmoto said:
Try clearing data,cache,dalvik cache and reflashing the ROM..if all fails try to clear data and flash the stock ROM through fastboot mode.
Click to expand...
Click to collapse
I've made it all, but when reboot, there is the same data there....
Neither can't root the phone, when I make adb sideload supersu.zip, I receive a installation aborted error after verification of the file....
Any Ideas?
Thanks in advance
Jorge BCN said:
I've made it all, but when reboot, there is the same data there....
Neither can't root the phone, when I make adb sideload supersu.zip, I receive a installation aborted error after verification of the file....
Any Ideas?
Thanks in advance
Click to expand...
Click to collapse
Flash the stock ROM once more through boot loader http://forum.xda-developers.com/showthread.php?t=2542219
If you have TWRP installed and your data backed up, I would highly suggest formatting your phone. My phone was having heaps of trouble, including random reboots, the inability for factory data reset, it was slow, having wake time issues, all sorts of shiz. One reformat and it was all better.
MoseIlla said:
If you have TWRP installed and your data backed up, I would highly suggest formatting your phone. My phone was having heaps of trouble, including random reboots, the inability for factory data reset, it was slow, having wake time issues, all sorts of shiz. One reformat and it was all better.
Click to expand...
Click to collapse
What do you mean with reformat? I can't boot into other recovery than stock, and it doesn't allow me erase user data, thats the problem.
When I try to flash other recovery (TWRP, Philz,..) it seems that has been flashed ok but when go to recovery from bootloader menu I have the old stock recovery menu...
Thanks in advance
Jorge BCN said:
What do you mean with reformat? I can't boot into other recovery than stock, and it doesn't allow me erase user data, thats the problem.
When I try to flash other recovery (TWRP, Philz,..) it seems that has been flashed ok but when go to recovery from bootloader menu I have the old stock recovery menu...
Thanks in advance
Click to expand...
Click to collapse
You unlocked the bootloader then, yes? How's your ROM behaving?
MoseIlla said:
You unlocked the bootloader then, yes? How's your ROM behaving?
Click to expand...
Click to collapse
Can you be more explicit?
Are you using the special mfastboot or the generic fastboot executable from the Android SDK?
Execute these commands with the phone in fastboot (bootloader menu):
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
liveroy said:
Are you using the special mfastboot or the generic fastboot executable from the Android SDK?
Execute these commands with the phone in fastboot (bootloader menu):
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Click to expand...
Click to collapse
Hi, the same after rebooting, I have all my user data... (I'm using mfastboot for OSX, but the same result with fastboot under Darwin subfolder of stock firmware)
no errors executing it, no errors in the phone, but no effect in phone user data
$ ./mfastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.017s
$ ./mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.018s]
finished. total time: 0.019s
$ ./mfastboot reboot
Jorge BCN said:
Can you be more explicit?
Click to expand...
Click to collapse
I just reread your first post. When did your phone start giving you errors? Did you install any new apps, did you let it die completely? The errors had to have started somewhere. Perhaps we can undo a bit of the damage that lead to this and get you back to a somewhat usable state if we have that information.
MoseIlla said:
I just reread your first post. When did your phone start giving you errors? Did you install any new apps, did you let it die completely? The errors had to have started somewhere.
Click to expand...
Click to collapse
No idea. There was not anything special or new app. A month ago it started to give errors. Sometimes I can get 1 or 2 minutes working without errors, but can't delete user data or reset from phone menu (no result when touch the button).
Thanks
Jorge BCN said:
No idea. There was not anything special or new app. A month ago it started to give errors. Sometimes I can get 1 or 2 minutes working without errors, but can't delete user data or reset from phone menu (no result when touch the button).
Thanks
Click to expand...
Click to collapse
Does this coincide with a firmware update (Like Android 4.4.2 to 4.4.3)?
MoseIlla said:
Does this coincide with a firmware update (Like Android 4.4.2 to 4.4.3)?
Click to expand...
Click to collapse
Nopes, as far as I know
Here's what I know about the issue, perhaps it will give someone else an idea:
1. The issue is either caused by or is unaffected by previous factory resets.
2. The issue is either caused by or is unaffected by the installation of new and/or updated ROMs.
3. If it's the same issue I was having, and I believe that it least shares the same root cause, then it is something that gets worse over time; it causes system instability (system UI crashes in increasing number, random reboots, etc...), slowness, and refuses to allow you to hard reset after a while.
4. In the case that it is the same issue, it has different effects on different methods of factory resets. In TWRP the factory reset process just continues on forever, until you hard reboot the device or until the battery drains out. If you press the factory reset button in fastboot it just resets to system, making no changes.
5. In TWRP I used the reformat option and have since had no issues, including better than new performance with crDroid.
Based on my understanding of the Moto G partition tables, I believe that the issue may have to do with gradual data corruption, possibly on the storage partition. This may be because of a software bug in the firmware or maybe a hardware issue. Due to the ubiquity of the lock up/reboot issue, which is well documented and has several guides indicating that a factory reset is in order when this occurs, I'm thinking that it is safe to assume that some resource shared both with the system and storage partitions is to blame.
If that is the case, then I would think it's the cache or a bug with an updated system app that leaves traces in the device storage.
This is all assuming the issues are interrelated, so I may be way off base, but if my assumptions are correct, then the only suggestion I can think of is to completely clear the device storage and cache and then try to factory reset again, as it may be hanging up on removing something there and aborting when it runs into trouble.
Maybe someone has a better idea. Your device may be bricked and since you unlocked the boot loader AFTER the issues started, you voided your warranty with none of the advanced recovery tools that you'd have with a custom recovery.
In other words: You might have to get a new phone.
Hey guys, love all the work that goes on in this forum.
I've run into a bit of a problem. My mate gave me his phone to try and fix after he interrupted a factory reset. It's stuck in a bootloop.
It's a RAZR HD and was originally from Telstra (Aus).
I've managed to unlock the bootloader, but quickly after that everything has gone to hell.
When I turn the phone on, it gives the bootloader is unlocked message. Then the android installation guy comes up and after about 5 seconds of trying to install the phone bootloops.
I am able to enter the Android System Recovery (3e) and have done factory reset/wipe data and wipe cache options, however does not change anything. When I press reboot system, the bootloop continues as if I did nothing. I have tried installing a ROM from an SD card however it fails at the Verifying Package stage. I am unable to adb push anything as usb debugging wasn't turned on.
I am able to enter into fastboot and can see my device however cannot flash any images from there for some reason using the fastboot commands (it comes up with a <bootloader> variable not supported! error: cannot load '[name of image file]'
I was able to use RSD Lite to flash the official Telstra ROM to the phone, however at the very end of the installation when it rebooted, it just went into the bootloop again.
Any help would be muchly appreciated.
Thanks guys!
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
piCARSO said:
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
Click to expand...
Click to collapse
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
bweN diorD said:
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
Click to expand...
Click to collapse
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
piCARSO said:
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
Click to expand...
Click to collapse
yes, thats correct.
I can't use my phone, it needs the older Google account in order to keep using it, but I don't remember the details. Is there a way to bypass this?! It's really stupid. iPhones has this sort of protection but Apple keeps track of its users so it makes sense... Now if you do a mistake here your phone is useless?! Or, there's a fix for it
Thanks
You can try to unlock bootloader and see if that works. Someone did data wipe on official firmware, with root and recovery if never asks
FreiKhost said:
I can't use my phone, it needs the older Google account in order to keep using it, but I don't remember the details. Is there a way to bypass this?! It's really stupid. iPhones has this sort of protection but Apple keeps track of its users so it makes sense... Now if you do a mistake here your phone is useless?! Or, there's a fix for it
Thanks
Click to expand...
Click to collapse
If you have twrp you can easily fix it. If not then there is a way to flash persist partition to fix it.
djhulk2 said:
You can try to unlock bootloader and see if that works. Someone did data wipe on official firmware, with root and recovery if never asks
Click to expand...
Click to collapse
But how? I can't enable developer options
superac11 said:
If you have twrp you can easily fix it. If not then there is a way to flash persist partition to fix it.
Click to expand...
Click to collapse
If I install TWRP, can I then install back original recovery? I want the phone to look as new after
EDIT: I just realised I can't install TWRP because I can't transfer files to my phone! because on FRP the computer does not recognise the device, and I also can't use ADB push because I can't turn on developer settings. Also, recovery mode does not work. but Fastboot does..
Through fastboot you can root, install twrp, wipe phone completely. You unlock boatloader in fastboot mode. May give you error saying locked...but you sure can still wipe the phone. There isn't a Samsung counter when you root, and you can lock back to official
djhulk2 said:
Through fastboot you can root, install twrp, wipe phone completely. You unlock boatloader in fastboot mode. May give you error saying locked...but you sure can still wipe the phone. There isn't a Samsung counter when you root, and you can lock back to official
Click to expand...
Click to collapse
I did it! In another way without fastboot. But just to know: How can I install TWRP via fastboot, if I can't transfer the zip file to the phone?
Tool all in one, once in fastboot mode it'll show you connected. Recovery and flasher option, you can install twrp and magisk. Works on official rom and custom
You have no chance to access the phone without the code. Its the google FRP lock.
Yess i have solution inbox me ..
This is Factory Reset Protection (FRP) which is a built-in security feature of Android 5.1 and later.