I bricked my phone.
h850 open bootloader. i tried to format the internal storage. didnt made a backup. now it wants a password and my own one doesnt work. is there any chance to repair it?
thank you in advance!
What wants password? TWRP ?
Try to flash the latest v10e KZD file with LGUP.
on a side note: what will happen when all tries are gone? will it erase it self? there is nothing to loose for me if this is the case?!
kripo said:
on a side note: what will happen when all tries are gone? will it erase it self? there is nothing to loose for me if this is the case?!
Click to expand...
Click to collapse
I dont know that counter your talking about. After restoring a backup from TWRP I got an issue that it wont accept my pin code to enter the phone. I've followed the steps in this link and it deleted the pin code. I hope this will help you. Please post your result. http://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
Please delete ALL 5 files one by one. It worked for me every time.
ItsNewDroid said:
I dont know that counter your talking about. After restoring a backup from TWRP I got an issue that it wont accept my pin code to enter the phone. I've followed the steps in this link and it deleted the pin code. I hope this will help you. Please post your result. http://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
Please delete ALL 5 files one by one. It worked for me every time.
Click to expand...
Click to collapse
hm, i dont think that this is the same thing on my phone.
just to clarify what i did:
i flashed no-verity-opt-encrypt-2.1.zip
i erased userdata and cache in fastboot
i flashed LG-H85010E-Flashable.COMPLETE.zip and FLUENCE_HD24_PATCH.zip
and then my problem(screenshot) occurred
kripo said:
hm, i dont think that this is the same thing on my phone.
just to clarify what i did:
i flashed no-verity-opt-encrypt-2.1.zip
i erased userdata and cache in fastboot
i flashed LG-H85010E-Flashable.COMPLETE.zip and FLUENCE_HD24_PATCH.zip
and then my problem(screenshot) occurred
Click to expand...
Click to collapse
I never ever have seen such a screen
But I would guess that something went wrong when flashing 10E or the patch.
I recommend the following:
- Check if TWRP is still installed
- If yes, format data again
- Re-flash SuperSU or no-verity-opt-encrypt-2.1.zip
- Reboot
If you lost TWRP, you have to flash it again, format data etc.
I've done all the steps you have listed few times but never encountered this problem. Can you even access the TWRP menu? Maybe ask Miustone the developer of HD24? Please tell if you can access the TWRP and your files
BabelHuber said:
I never ever have seen such a screen
But I would guess that something went wrong when flashing 10E or the patch.
I recommend the following:
- Check if TWRP is still installed
- If yes, format data again
- Re-flash SuperSU or no-verity-opt-encrypt-2.1.zip
- Reboot
If you lost TWRP, you have to flash it again, format data etc.
Click to expand...
Click to collapse
after formatting data in TWRP the new screen appears, thanks for that. but the bar in the new screen(screenshot) doesn't change.
the button beneath the bar makes the phone going into recovery and format cache.
repair data after format data did the trick! thanks everyone for the fast help!!! love you all
Related
No matter what I do, I cannot get a single thing to flash anymore with CWM. I'm on the dark side rom, unlocked bootloader & rooted, 4.5.91, and using romracers 4.0.1.5 cwm recovery. I even tried tenfars and the one rom manager gives me, but the problem persisted. Is there any fix for this because it is getting VERY frustrating!
The only fix available would be to figure out what you've done. The CWM versions all work fine and don't require a fix. It's something at your end and with the information you've given, there's not much to go on.
It must corrupt the files when I transfer them from the computer to the phone. I've downloaded straight from the source and MANY other sources of the exact same rom/kernal/ect... and it all ends up not working. Is it better to download on the phone? Oh, missed one detail but I don't think it matters, I'm using a mac and when I download a file it auto unzipps, then I just re-compress it and throw it on the phone. Would that affect anything?
change ur cable... try different machine...
Same problem
I've encountered the same problem! I flashed darkside on my rooted AT&T Atrix, (unlocked bootlader, rooted). My friend borrowed my phone and saw the AT&T system update and installed it. the phone reboots and I couldn't move past that, then i got the little green android dude with the /!\ sign behind him. Tried factory resetting, restoring from backup, and even flashing over Gingerbread, but nothing worked! If you have found a fix, an answer would really be appreciated!
dcben09 said:
I've encountered the same problem! I flashed darkside on my rooted AT&T Atrix, (unlocked bootlader, rooted). My friend borrowed my phone and saw the AT&T system update and installed it. the phone reboots and I couldn't move past that, then i got the little green android dude with the /!\ sign behind him. Tried factory resetting, restoring from backup, and even flashing over Gingerbread, but nothing worked! If you have found a fix, an answer would really be appreciated!
Click to expand...
Click to collapse
Not the same problem! You tried to OTA on an unlocked bootloader.
CaelanT said:
Not the same problem! You tried to OTA on an unlocked bootloader.
Click to expand...
Click to collapse
Would you happen to know how I might go about fixing it?
Gfrt94yn said:
Oh, missed one detail but I don't think it matters, I'm using a mac and when I download a file it auto unzipps, then I just re-compress it and throw it on the phone. Would that affect anything?
Click to expand...
Click to collapse
That's probably your problem right there. Use a Windows machine to download to, put the zip file on your phone from Windows, do a FULL fastboot wipe, and try flashing the ROM. (Or download right to your phone).
Sorry, I don't use a mac, so can't help there. I can tell you that just zipping files without the correct compression settings will cause the flash to fail.
e.g. If using 7-Zip you need to set Archive format to "zip" and Compression level to "store" when creating flashable zip files or they won't work.
In any event, do a FULL fastboot wipe before flashing:
reboot to recovery
wipe dalvik
wipe cache
reboot to fastboot
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot reboot (to recovery)
flash ROM
There are a couple of scripts in the forums which are almost completely automated to do this.
Actually I figured this out forever ago (moved on to new phone), but I'll still help. Anyway download the file DIRECTLY to your phone, no computers!! Then place it on root of sd card (for convenience, you don't have to) and flash. Problem solved! if that doesn't work, the file is most likely corrupt or the way your phone downloaded it is outta wack. Hope this helped
Sent from my SAMSUNG-SGH-I727 using XDA App
Gfrt94yn said:
Actually I figured this out forever ago (moved on to new phone), but I'll still help. Anyway download the file DIRECTLY to your phone, no computers!! Then place it on root of sd card (for convenience, you don't have to) and flash. Problem solved! if that doesn't work, the file is most likely corrupt or the way your phone downloaded it is outta wack. Hope this helped
Sent from my SAMSUNG-SGH-I727 using XDA App
Click to expand...
Click to collapse
Please see my post right before your post. Your problem was downloading to a MAC and the files being unzipped. Then when you zipped them back up it was not done correctly. Computers are not the problem!
Hey, I'm running TWRP 2.5.0.2 [http://forum.xda-developers.com/showthread.php?t=2292565] and after I flashed a new rom [http://forum.xda-developers.com/show...php?t=2301724] and rebooted TWRP is asking me for a password? Just curious if anyone else has had this problem?
Whenever I don't boot into recovery it says encryption failed. it says to do a factory reset and encrypt the device again.
Edit: I was able to get it working again.
I've seen that before, it was the same time that if I tried to create a nandroid it said there was about 700gb in data. After doing resets and such it would still come back. Only way I got it to go away was by flashing back to stock and re-rooting
obsidianfirefly said:
I've seen that before, it was the same time that if I tried to create a nandroid it said there was about 700gb in data. After doing resets and such it would still come back. Only way I got it to go away was by flashing back to stock and re-rooting
Click to expand...
Click to collapse
Thanks, I'm still getting used to how this phone works. Xperia Play was much easier.
Schwabie64 said:
Hey, I'm running TWRP 2.5.0.2 [http://forum.xda-developers.com/showthread.php?t=2292565] and after I flashed a new rom [http://forum.xda-developers.com/show...php?t=2301724] and rebooted TWRP is asking me for a password? Just curious if anyone else has had this problem?
Whenever I don't boot into recovery it says encryption failed. it says to do a factory reset and encrypt the device again.
Edit: I was able to get it working again.
Click to expand...
Click to collapse
So how did you get it working? Happened to me earlier this week. Had to flash to stock.
dwmartin6341 said:
So how did you get it working? Happened to me earlier this week. Had to flash to stock.
Click to expand...
Click to collapse
Sorry, I had to do the same [flash back to stock]. Not sure what caused it to happen though.
Use the verw first version of TWRP
Schwabie64 said:
Sorry, I had to do the same [flash back to stock]. Not sure what caused it to happen though.
Click to expand...
Click to collapse
I got the same problem with my Nexus 7 (2013) when using the lastest version of twrp (v2.6.3.0).
I didn't encounter this issue when I used the very first version: openrecovery-twrp-2.6.0.0-flo.img
can someone tell me how to fix this even i have the same issue
kindrudekid said:
can someone tell me how to fix this even i have the same issue
Click to expand...
Click to collapse
I use this recovery now.
http://forum.xda-developers.com/showthread.php?t=2292112
twrp 2.6.1.0 is asking for password
Hey guys been reading alot of discussion and threads in this site to figure out how am i gonna solve this issue. I really don't why the twrp is always asking for password. I wipe everything from carrier to dalvik cache and selected factory reset but eventually i am still stock to this password. I did try to revert the version of twrp but it wasn't successful. It says "FAILED" after installation. I haven't use my phone (gt-n7100), i think, for a month because of this. I badly need your expertise guys. Thanks. Hoping to hear from this community.
Just as I enter TWRP recovery, it asks for a password. I clearly remember that I hadn't set any password. But there is another option "cancel". On pressing that button I enter the normal functions of TWRP recovery. The password is not creating any problems but I would like to put up on for security. Any help guys?
Hi all,
I recently got a new Axon 7 (A2017U) and wanted to root it just like my old G3. I tried following DrakenFX's instructions (Here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), but I got lost. I ended up with a password being requested at the android startup screen. In a panic, I clicked Format Data when I got back into TWRP, that made it worse and I went into EDL to see if that might help. Eventually I got back into TWRP and that's where I am now, desperately trying to get my new phone working again. All the threads I read only add another layer of confusion. Would someone be willing to walk me through the steps of fixing my phone? I really don't want to RMA/have $400 to go down the drain. I'd own you a big one.
-RG
video_dewd said:
Hi all,
I recently got a new Axon 7 (A2017U) and wanted to root it just like my old G3. I tried following DrakenFX's instructions (Here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), but I got lost. I ended up with a password being requested at the android startup screen. In a panic, I clicked Format Data when I got back into TWRP, that made it worse and I went into EDL to see if that might help. Eventually I got back into TWRP and that's where I am now, desperately trying to get my new phone working again. All the threads I read only add another layer of confusion. Would someone be willing to walk me through the steps of fixing my phone? I really don't want to RMA/have $400 to go down the drain. I'd own you a big one.
-RG
Click to expand...
Click to collapse
Hi,
so you have access to the TWRP. Thats good. Do you have access to a stock ROM from your manufacturer? In case yes, you could simply flash the stock.
For this, the rom has to be on a SD card or on the internal memory of the phone.
In TWRP go to "Install", than navigate to the file and swipe to install (it comes a zip file).
mugel2110 said:
Hi,
so you have access to the TWRP. Thats good. Do you have access to a stock ROM from your manufacturer? In case yes, you could simply flash the stock.
For this, the rom has to be on a SD card or on the internal memory of the phone.
In TWRP go to "Install", than navigate to the file and swipe to install (it comes a zip file).
Click to expand...
Click to collapse
I'm looking for one. Some threads pointed to an OTA update that ZTE has on their site. However, when I try to install things on TWRP, I get an error about "dev/block/sde14" being read-only. (It sometimes says "sde13" too.)
video_dewd said:
I'm looking for one. Some threads pointed to an OTA update that ZTE has on their site. However, when I try to install things on TWRP, I get an error about "dev/block/sde14" being read-only. (It sometimes says "sde13" too.)
Click to expand...
Click to collapse
Dis you go on Advanced
Wipe dalvik-chace
Wipe /cache
Do you have access to fastboot?
mugel2110 said:
Dis you go on Advanced
Wipe dalvik-chace
Wipe /cache
Do you have access to fastboot?
Click to expand...
Click to collapse
Yes and I'm not sure. I can boot to system, recovery, and bootloader.
video_dewd said:
Yes and I'm not sure. I can boot to system, recovery, and bootloader.
Click to expand...
Click to collapse
I am far from being a pro. I once had the problem that I was caught in bootloop and could not install a new rom. But I was able to re-flash TWRP (via Minimal adb and fastboot) and than everything was fine.
Maybe someone else can comment on that. On your own risk...
Just a tip. Never panic and press any button
mugel2110 said:
Just a tip. Never panic and press any button
Click to expand...
Click to collapse
I figured haha
So I wanted to factory reset my phone today to start fresh. I tried to do the normal reset on the phone but it kept bringing me to the TWRP screen. I read a few posts on how to reset and it said use the TWRP Wipe. I did the normal TWRP wipe. It said it only deletes cache and dalvik and data and keeps your internal storage. So I swiped and then restarted my phone as it did it for me. Now I've tried rebooting multiple times and no luck. I checked my internal storage and it has gone and deleted the internal. So what do I do now? I have a phone which only goes to recovery. I had backed up my LG using bridge.
Also not sure if i posted in the right area. Not sure how to move it if so?
Janny1993 said:
So I wanted to factory reset my phone today to start fresh. I tried to do the normal reset on the phone but it kept bringing me to the TWRP screen. I read a few posts on how to reset and it said use the TWRP Wipe. I did the normal TWRP wipe. It said it only deletes cache and dalvik and data and keeps your internal storage. So I swiped and then restarted my phone as it did it for me. Now I've tried rebooting multiple times and no luck. I checked my internal storage and it has gone and deleted the internal. So what do I do now? I have a phone which only goes to recovery. I had backed up my LG using bridge.
Also not sure if i posted in the right area. Not sure how to move it if so?
Click to expand...
Click to collapse
What model do you have?
Without that info you will not get much help.
wolfu11 said:
What model do you have?
Without that info you will not get much help.
Click to expand...
Click to collapse
LG G5 H850 - V20K-EUR-XX - Not sure about anything else but thats all I could remember before resetting the phone. I live in the UK and the phone was unlocked to all networks.
I am currently downloading H85020K_00_OPEN_EU_0822.kdz but not sure if that file is even needed.
Janny1993 said:
LG G5 H850 - V20K-EUR-XX - Not sure about anything else but thats all I could remember before resetting the phone. I live in the UK and the phone was unlocked to all networks.
I am currently downloading H85020K_00_OPEN_EU_0822.kdz but not sure if that file is even needed.
Click to expand...
Click to collapse
It sounds like you wiped your OS so yeah you're going to need to reinstall it. I'm pretty sure auto prime has a h850 zip file so you can Flash via TWRP look it up.
wolfu11 said:
It sounds like you wiped your OS so yeah you're going to need to reinstall it. I'm pretty sure auto prime has a h850 zip file so you can Flash via TWRP look it up.
Click to expand...
Click to collapse
Finally figured it out.
I used volume + and power button to get into the firmware update/download screen and used the LG Bridge (software update error recovery) and it did it all for me. Thanks for the help
Hey guys, I would like to ask for advice.
My phone suddenly stuck at this screen:
Android Recovery
Xiaomi/laurel_sprout_eea/laurel_sprout
10/QKQ1.190910.002/V11.0.2.0.QFQEUXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
Its very similar to an issue already discussed on this site: https://forum.xda-developers.com/mi-a2/help/xiao-mi-a2-load-android-t3993067?nocache=1
However, in my case, i'm unable to access the Recovery menu. It results in Error screen: https://imgur.com/a/2rPDGQa
I would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
Thanks for your help!
If you have already unlocked bootloader, flash TWRP, make backup of all partitions and copy it to the PC. If you're still with locked bootloader, then I'm afraid you're out of luck. There is probably no way how to restore user data.
Also happened to me not long ago, interesting, did you do some system changes before that?
alexandarpb said:
Also happened to me not long ago, interesting, did you do some system changes before that?
Click to expand...
Click to collapse
No, I don't think so. Although there might had been some kind of a system update few hours before.
_mysiak_ said:
If you have already unlocked bootloader, flash TWRP, make backup of all partitions and copy it to the PC. If you're still with locked bootloader, then I'm afraid you're out of luck. There is probably no way how to restore user data.
Click to expand...
Click to collapse
Hi @_mysiak_ I'm in a similar situation (Mi A3 too) but instead of eMkoC4, I can access to Recovery menu. Is there anything I can do to recover some data?
Thanks in advance, Simone
simogere said:
Hi @_mysiak_ I'm in a similar situation (Mi A3 too) but instead of eMkoC4, I can access to Recovery menu. Is there anything I can do to recover some data?
Thanks in advance, Simone
Click to expand...
Click to collapse
I would try pulling the data via ADB (if you have it enabled) in stock recovery. I am not sure how it will behave with encryption, but it's worth a try. Boot into recovery on the phone, connect it to the PC and use this command on the PC:
"adb pull /storage/emulated/0"
_mysiak_ said:
I would try pulling the data via ADB (if you have it enabled) in stock recovery. I am not sure how it will behave with encryption, but it's worth a try. Boot into recovery on the phone, connect it to the PC and use this command on the PC:
"adb pull /storage/emulated/0"
Click to expand...
Click to collapse
Hi @_mysiak_ thanks for the reply. I'm quite sure I've never enabled USB debugging
simogere said:
Hi @_mysiak_ thanks for the reply. I'm quite sure I've never enabled USB debugging
Click to expand...
Click to collapse
In such case I'm afraid that you're out of luck as well (it probably wouldn't work anyway due to encryption).