Related
UPDATING YOUR RADIO
IMPORTANT - READ ALL OF THIS POST
I originally wrote this post for Kang-o-rama but, considering everybody will need to update their radio at some stage, though I would x-post it here. Hopefully a mod will sticky, at least for the next three or four weeks.
You phone is designed to support updating the radio image. The radio image is primarily used to control the mobile communication of your phone. Other functions are sometimes offloaded to the radio cpu including, in the case of the Nexus, some video processing. Because of the codependencies between the radio, the kernel and the rom, it is occasionally necessary to update your radio.
Froyo (Android 2.2) requires a new radio and so does CyanogenMod 6.0 and Kang-o-rama 1.0.
Updating your radio is safe if you do it properly and carefully. It is very unsafe if you do not. One of the consequences of a failed radio update is a bricked (useless) phone. This risk is not the same when updating a kernel or a rom.
To update your radio to a suitable version for Kang-o-rama 1.0, Froyo or CyanogenMod 6.0 using fastboot follow the following instructions below carefully. The scope of this guide does not extend to getting fastboot working on your computer and your phone connected. Please see the sticky threads in this forum and search for additional information if you are unsure.
Fully charge your phone
Download the radio image from the link below
Compare the MD5 checksum of the file you downloaded with the one printed below. This is very important, please do it. For Windows or OSX you can use the free HashTab application.
Connect your phone to your computer
Reboot your phone into the bootloader (fastboot mode)
At the command prompt on your computer type: fastboot devices
A value like HTXXXXXXXXXXX should be displayed with the word fastboot next to it
Your phone screen should have FASTBOOT USB on it
If all of the above is not exactly as described DO NOT PROCEED and resolve your fastboot problem
To proceed, make sure your downloaded file is in your current directory
At the command prompt type: fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img - you must type it correctly!
Now, observe the computer and be patient TOUCH NOTHING!!
The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
Watch the little indicator at the top of your phone screen.
Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
Then, and only then, reboot your phone.
Your phone should reboot to your normal home screen and you should get a mobile connection.
Remember, if you're still using an older rom some things won't work. Best you now upgrade to Kang-o-rama 1.0!
Download: froyo-radio-32.36.00.28U_4.06.00.02_2.img
MD5 Checksum: 3321c196d8ec1cf748fd20c3c4068520
Take care.
Reserved for who only knows what...
Is there a zip file that can be downloaded to the N1? I don't have access to a computer,at least not for awhile.
after the cmd says writing radio it finishes and my phone stays on the fastboot screen. I can use the volume buttons to move the selector and reboot but the radio on the fastboot screen still says RADIO-4.06.00.12.7
when u use fastboot , it doesnt reboot itself n u have to reboot it urself and after it has flashed in fastboot u are safe to do anything but only after the red bar on the top right corner disappears. Red one comes after green one. Then u have to type fastboot reboot or use the menu to reboot. It will do nothing magical after than but boot straight to the system. U mixed up recovery flashing and fastboot
how about flash via Recovery ? I think its safer and much more convenient
U r most probably gonna f up using recovery. My experience some days ago with my cliq lol
cronin4392 said:
after the cmd says writing radio it finishes and my phone stays on the fastboot screen. I can use the volume buttons to move the selector and reboot but the radio on the fastboot screen still says RADIO-4.06.00.12.7
Click to expand...
Click to collapse
I'm having this same exact issue. I followed the instructions exactly all the way to reboot.
It's weird because the 720p mod works fine afterwards where before it would crash the phone when trying to record or open the camera settings.
Man please someone anyone help me. i have done exactly what the steps say and fastboot wont comply. all i get is C:\Users\Whoisc_walk>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.
img
error: cannot load 'froyo-radio-32.36.00.28U_4.06.00.02_2.img'
im not really sure what i did wrong. i think it may be the directory but as far as i know its in the correct one. so im getting frustrated so im asking for help
figured it out it was a directory problem
C_walk said:
Man please someone anyone help me. i have done exactly what the steps say and fastboot wont comply. all i get is C:\Users\Whoisc_walk>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.
img
error: cannot load 'froyo-radio-32.36.00.28U_4.06.00.02_2.img'
im not really sure what i did wrong. i think it may be the directory but as far as i know its in the correct one. so im getting frustrated so im asking for help
figured it out it was a directory problem
Click to expand...
Click to collapse
Have to be in the directory where fastboot is.. from there you can flash the Radio.
I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s
silentfishwm said:
I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s
Click to expand...
Click to collapse
Try downloading the img again, check the MD5.
Also make sure your battery is fully charged.
djmcnz, thanks for your help, I double checked the MD5, it's correct and the phone was fully charged. Any other possible cause of this error?
djmcnz said:
Try downloading the img again, check the MD5.
Also make sure your battery is fully charged.
Click to expand...
Click to collapse
silentfishwm said:
djmcnz, thanks for your help, I double checked the MD5, it's correct and the phone was fully charged. Any other possible cause of this error?
Click to expand...
Click to collapse
You are running a rooted phone with a custom recovery image correct?
silentfishwm said:
I always got "verify fail" messages, could anyone help me? Thanks
C:\Downloads\android>fastboot flash radio froyo-radio-32.36.00.28U_4.06.00.02_2.img
sending 'radio' (26112 KB)... OKAY [ 3.656s]
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 7.609s
Click to expand...
Click to collapse
Is your bootloader unlocked? Or did you root without unlocking the bootloader?
________________________
N1 w/ XDA App
Ooopps.... I'm using a rooted phone with locked bootloader, I'm an idiot
Is there anyway for my phone to make a radio update?
djmcnz said:
You are running a rooted phone with a custom recovery image correct?
Click to expand...
Click to collapse
J.L.C, yes I rooted my phone without unlocking the bootloader...
Any way to update radio in such case?
J.L.C. said:
Is your bootloader unlocked? Or did you root without unlocking the bootloader?
________________________
N1 w/ XDA App
Click to expand...
Click to collapse
silentfishwm said:
J.L.C, yes I rooted my phone without unlocking the bootloader...
Any way to update radio in such case?
Click to expand...
Click to collapse
In that case you have to update the radio though recovery with a zip file.
________________________
N1 w/ XDA App
Thanks J.L.C., I have got the radio updated with an update.zip
J.L.C. said:
In that case you have to update the radio though recovery with a zip file.
________________________
N1 w/ XDA App
Click to expand...
Click to collapse
I have an unlocked g1 for at&t if I update the radio will I have to unlock it again
Hey everyone, even though I dont have this device I figured it'd be good to have this thread so I'll start it.
This thread will contain all zips / firmwares for the device as well as changelogs if anyone wants to supply it. The zips will be flashable through bootloader not through recovery (I dont want to deal with the issues of "Well I bricked it because my recovery locked up" or however the hell you manage to break it.)
Download links:
M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7 Firmware zip
Code:
Changelog for 1.29.651.10
- BlinkFeed improvements
- New Sprint Zone client
- Improved Back and Home key sensitivity
Any more files someone wants to provide feel free to PM me or post them here.
Is this the ota that's flashable for us rooted people
Sent from my HTCONE using Tapatalk 2
It's the firmware to flash through bootloader....
Thanks.
Sent from my Nexus 10 using Tapatalk HD
Is this safe for root or is this just a manuel upload instead of waiting for the OTA?
Should we flash the firmware or is it
Ok to just wait for a rooted Rom to be made with the new firmware and just flash that. I guess my question is are we going to be missing any key components by not taking it directly from HTC like newer radios
Sent from my HTCONE using xda premium
Nice to see you here Noob.
And it's OTAs. Official updates.
D3rped out Beastmode! HTC ONE!
gonowhere said:
Is this safe for root or is this just a manuel upload instead of waiting for the OTA?
Click to expand...
Click to collapse
fastboot oem rebootRUU
fastboot flash zip FIRMWARENAME.zip
fastboot reboot
Just installs new firmware for you. Doesnt actually affect your rom. Will wipe recovery though because there is no s-off.
dandan2980 said:
Should we flash the firmware or is it
Ok to just wait for a rooted Rom to be made with the new firmware and just flash that. I guess my question is are we going to be missing any key components by not taking it directly from HTC like newer radios
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
You flash the firmware because I believe the boot.img and tp.img are new. Haven't checked because I dont have an image dump to compare. But without s-off we cant flash selectively.
thronnos said:
Nice to see you here Noob.
And it's OTAs. Official updates.
D3rped out Beastmode! HTC ONE!
Click to expand...
Click to collapse
Still don't have a phone though. Kinda bums me out but because I got fired I can't afford the upgrade now. :/
And I'm less of a newb than you
So we can flash this through CMD WITHOUT HAVING STOCK RECOVERY. It will just erase twrp and we need to reflash twrp again??? Then flash stock rooted.
Sent from my HTCONE using xda premium
Dev-Host is borked
First of all, thank you for sharing it! I was waiting for CyanogenMod to update their ROM but they haven't yet.
I clicked on the link but it doesn't download the file after clicking on "download"
Any advice?
Thanks!
chamo311 said:
I clicked on the link but it doesn't download the file after clicking on "download"
Any advice?
Thanks!
Click to expand...
Click to collapse
Mine took me to a page not found the first time, but refreshing the page worked. Also, make sure you're clicking the right "download" button, as I had a couple ads with larger download buttons related to the ads.
Now my turn for a question. I tried flashing it and it failed. Anyone have an idea why? Here's what fastboot reported:
Code:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.063s
C:\Android>fastboot flash zip M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7
-Firmware.zip
sending 'zip' (15538 KB)...
OKAY [ 1.809s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.059s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.044s
No harm done, but I'm still on 1.29.651.7
Thanks! I downloaded it!
Hmmm no idea, I haven't flashed mine yet....I'm away from a computer. I'll let you know.
Thanks again!
kzibart said:
Mine took me to a page not found the first time, but refreshing the page worked. Also, make sure you're clicking the right "download" button, as I had a couple ads with larger download buttons related to the ads.
Now my turn for a question. I tried flashing it and it failed. Anyone have an idea why? Here's what fastboot reported:
Code:
C:\Android>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.048s]
finished. total time: 0.063s
C:\Android>fastboot flash zip M7_WL_JB_50_SPCS_Sprint_WWE_1.29.651.10-1.29.651.7
-Firmware.zip
sending 'zip' (15538 KB)...
OKAY [ 1.809s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.059s
C:\Android>fastboot reboot
rebooting...
finished. total time: 0.044s
No harm done, but I'm still on 1.29.651.7
Click to expand...
Click to collapse
when you get that error just retype the fastboot flash command again immediately after you recieve the error and it should go then.
Aldo101t said:
when you get that error just retype the fastboot flash command again immediately after you recieve the error and it should go then.
Click to expand...
Click to collapse
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
kzibart said:
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
Click to expand...
Click to collapse
Have you checked the MD5 of the .zip?
kzibart said:
I tried that (about 8 times) and still the same error each time. I even tried a shorter USB cable (which someone elsewhere suggested as a fix for this error), but no dice. So then I tried restoring the factory recovery and letting it take the update OTA. When the update started, it rebooted into recovery and then the screen went black with the red/orange led on for about 20 seconds, off for 5, repeating like that. I let it sit for a good 30 minutes before giving up. I had to long-press the power for 20 seconds to get it to reboot.
Still no harm done, but I'm still stuck on 1.29.651.7.
Click to expand...
Click to collapse
YES, i tried this also and got the same results.
Aldo101t said:
YES, i tried this also and got the same results.
Click to expand...
Click to collapse
Same here......FAILED for me too
aschlect said:
Same here......FAILED for me too
Click to expand...
Click to collapse
Are you guys SuperSu instead of Koush's Superuser?
jaytv said:
Are you guys SuperSu instead of Koush's Superuser?
Click to expand...
Click to collapse
Yes, I am SuperSU
I have just unlocked the Bootloader, and now I am trying to install TWRP recovery. I have tried the manual method through the command prompt, and also through Hasoon2000's toolkit. I just receive this error:
sending 'recovery' (7912 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.005s
I've tried reinstalling drivers, but that doesn't seem to solve it. I've also tried different USB ports. Has anyone encountered this error? Does anyone have a solution? Thanks.
Did you reboot your PC after uninstalling the drivers? Are you using a USB3 port? Win8?
bigdaddy619 said:
Did you reboot your PC after uninstalling the drivers? Are you using a USB3 port? Win8?
Click to expand...
Click to collapse
I didn't reboot, I'm gonna do that now; and yes, it's USB3, so probably gonna move to USB2? I'm on Win7.
Fired334 said:
I didn't reboot, I'm gonna do that now; and yes, it's USB3, so probably gonna move to USB2? I'm on Win7.
Click to expand...
Click to collapse
Yeah USB 3 ports are kinda finicky sometimes also have you updated your android-sdk files lately there have been quite a few updates the past couple weeks including drivers.
bigdaddy619 said:
Yeah USB 3 ports are kinda finicky sometimes also have you updated your android-sdk files lately there have been quite a few updates the past couple weeks including drivers.
Click to expand...
Click to collapse
No I haven't. I wasn't keeping up with the HTC One; I just received it. (Moving over from GNex)
Okay, I uninstalled drivers, restarted PC, used a USB2 port, and the TWRP flash was finally successful. :victory: Thanks. I should've known to do those steps.
sending 'recovery' (7912 KB)
OKAY [ 1.099s]
writing 'recovery'...
OKAY [ 0.639s]
finished. total time: 1.740s
Fired334 said:
Okay, I uninstalled drivers, restarted PC, used a USB2 port, and the TWRP flash was finally successful. :victory: Thanks. I should've known to do those steps.
sending 'recovery' (7912 KB)
OKAY [ 1.099s]
writing 'recovery'...
OKAY [ 0.639s]
finished. total time: 1.740s
Click to expand...
Click to collapse
Cool glad you got it enjoy
bigdaddy619 said:
Cool glad you got it enjoy
Click to expand...
Click to collapse
Thanks, looking forward to using my awesome-looking One.
Sloth said:
Did you reboot your PC after uninstalling the drivers? Are you using a USB3 port? Win8?
Click to expand...
Click to collapse
how can i uninstall adb??
getting the same problem
I spent A few hours or so trying to unlock and than root my phone. I have been unable to unlock the bootloader so far, i think.
I ran my IMEI to make sure i was running the right stuff for the right phone.
im getting stuck at the point where you run fastboot to unlock with the token generated by following HTC Dev's bootloader, or really, right after it.
when i do this:
C:\>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.150s
From the various articles ive read, your supposed to get some prompt or option on your phone to unlock the bootloader, but i never see this option on my phone? could it be because my bootloader is unlocked?
Since im new and am not allowed to post external links yet, a screen shot of my bootloader on imgur at /a/JV4eJ
Looking at the image, i think my phone's bootloader is allready unlocked?
Where im hitting a wall is when trying to get the TWRP custombackup to work
I keep getting this error.
C:\>fastboot flash recovery twrp.img
target reported max download size of 1514139648 bytes
sending 'recovery' (20020 KB)...
OKAY [ 2.373s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 2.400s
I've tried renaming it to twrp.img, and leaving it as twrp-3.1.1-0-hima.img
I have an old hboot on this phone, and read somewhere that i should try an 2.8.7.*.img, so i did aswell, but they all produce the above results.
Any adivce and feedback is much appreciated, and thanks for reading.
The end goal for me is tied into this guide which i have been following
Are you in download mode?
Sent from my HTC One M9 using Tapatalk
lazyguyMC said:
Are you in download mode?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
I am not sure. I reboot my phone via adb and it boots to a normal home screen. Ive tried it from there with no luck. IM trying it from the bootloader screen( im assuming this is not the download screen?) If thats the problem, than i am abit confused on how to get to download mode. ive tried adb reboot download, but it just puts be back at the main os screen.
The download mode screen is similar to a stock Android recovery screen. It is black and has many options like show info, show barcodes, reboot to download mode, reboot to bootloader, etc etc. To go in there, shut down your phone, then press and hold volume down and power. Then, you should be able to unlock your bootloader. (Make sure Enable OEM unlock is checked in developer options.)
Sent from my HTC One M9 using Tapatalk
lazyguyMC said:
The download mode screen is similar to a stock Android recovery screen. It is black and has many options like show info, show barcodes, reboot to download mode, reboot to bootloader, etc etc. To go in there, shut down your phone, then press and hold volume down and power. Then, you should be able to unlock your bootloader. (Make sure Enable OEM unlock is checked in developer options.)
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Maybe thats one of my issues. Reboot to download mode is not an option when i power down to the bootloader. And also, there was no option for me to enable oem unlock in the dev options.
is it possible the imei number i have is telling me lies?( the reason i ask, is when i run it, it says an m9, but when im in the bootloader it says *** Unlocked *** followed y this line : M7_WLS PVT SHIP S-ON RH
Hmm......You sure that isn't an MY?
Sent from my HTC One M9 using Tapatalk
imei.info tells me its an m9 and swappa tells me its an m7. im so confused. I tried using a key from htc dev for the m7 just abit ago, and it succeeds aswell, but im stil not prompted to unlock the phone.
It's definetely a M7 (the sprint version to be exactly) and not a M9. Those IMEI checks are more than inaccurate. You should always trust the infos in your bootloader. Alternatively, you can take a look at the serial number of the phone. There's a guide written by Llabtoofer (on his website) which explains how to "read" it.
If the bootloader already is unlocked then of course you won't see that prompt. And TWRP fails to flash since you can't flash M9 files on a M7 (at least if your phone isn't S-OFF and if it was you would gain a paperweight by doing so).
I contacted a fellow mod so that the thread will get moved to the correct forum.
OK so i got twrp installed and i attempted to get magisk to install but that failed, so i used SuperSu. I did what i wanted than unrooted and got rid of the twrp custom recovery. The problem is im failing my Safety Net. So after some tedious searching i found a stock rom for my phone, and re-flashed it. Im still failing safetynet with a fresh verified stock rom for my phone. I dunno where to look now in hopes in getting it to pass safety Net. Is it possible SuperSu left something behind? When i installed the Rom via a RUU.exe, wouldn't that have erased all the SuperSu breadcrumbs? i know in my hboot menu it says relocked(not tampered anymore).
brad35309 said:
OK so i got twrp installed and i attempted to get magisk to install but that failed, so i used SuperSu. I did what i wanted than unrooted and got rid of the twrp custom recovery. The problem is im failing my Safety Net. So after some tedious searching i found a stock rom for my phone, and re-flashed it. Im still failing safetynet with a fresh verified stock rom for my phone. I dunno where to look now in hopes in getting it to pass safety Net. Is it possible SuperSu left something behind? When i installed the Rom via a RUU.exe, wouldn't that have erased all the SuperSu breadcrumbs? i know in my hboot menu it says relocked(not tampered anymore).
Click to expand...
Click to collapse
What I would do is run the latest RUU. I've done so on my m7 and it always passes SafetyNet at that point. Make sure you back up anything you want to save first.
I will try reflashing via fastboot with my current rom. If that still fails, I'll try the latest. I'm just hesitant because it comes with the newest security patch, and I need one that's before the March 2017 patch
The last official update for the M7 got distributed in 2015. All RUUs for that Device will be on a security patch that is older than March 2017.
Sent from my HTC One M9 using XDA Labs
i downloaded the latest RUU, and i installed via the executable. it was successful, however i am still failing the safety net check. i attempted again via Fastboot, but i keep getting this error
C:\>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (45578 KB)...
OKAY [ 2.894s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 8.027s
i got the firmware from the same page as the post mentioned above. Do i have to do something special to get it to take?
brad35309 said:
i downloaded the latest RUU, and i installed via the executable.
Click to expand...
Click to collapse
Did you install version 6.23.651.10 from this thread using the exe? I've reset my phone after running custom ROMs using it and it passed SafetyNet fine afterward.
Hello guys. Thanks for tacking a look at this thread.
I have a P8Lite ALE-L21 that some time ago I seat my ass on it and screen broke and even bend a bit the frame. I have lots of pictures from a trip that I´m desperate thinking that maybe I will lose them.
First of all I brought a new frame with new screen. Replace the good looking board to new frame. Tried to turn on the phone and starts to loop trying to boot but never boots. I have read that this is an usual issue with this phones.
Now I´m stuck at the fastboot & rescue mode not knowing what to do next.
Is it possible to restore the phone to factory settings and after that try to recover the pictures? If it´s possible to restore it can someone give me some instruction on how to do it?
I will apriciate all the help from you guys.
Thanks
tcolaco said:
Hello guys. Thanks for tacking a look at this thread.
I have a P8Lite ALE-L21 that some time ago I seat my ass on it and screen broke and even bend a bit the frame. I have lots of pictures from a trip that I´m desperate thinking that maybe I will lose them.
First of all I brought a new frame with new screen. Replace the good looking board to new frame. Tried to turn on the phone and starts to loop trying to boot but never boots. I have read that this is an usual issue with this phones.
Now I´m stuck at the fastboot & rescue mode not knowing what to do next.
Is it possible to restore the phone to factory settings and after that try to recover the pictures? If it´s possible to restore it can someone give me some instruction on how to do it?
I will apriciate all the help from you guys.
Thanks
Click to expand...
Click to collapse
Hmm, if you have twrp dirty flash personas mod. If you don't, try t flash twrp, and after flash the mod. That won't delete your files, only make your phone to boot. Hopefully you had Android 6 already.
tcolaco said:
Hello guys. Thanks for tacking a look at this thread.
I have a P8Lite ALE-L21 that some time ago I seat my ass on it and screen broke and even bend a bit the frame. I have lots of pictures from a trip that I´m desperate thinking that maybe I will lose them.
First of all I brought a new frame with new screen. Replace the good looking board to new frame. Tried to turn on the phone and starts to loop trying to boot but never boots. I have read that this is an usual issue with this phones.
Now I´m stuck at the fastboot & rescue mode not knowing what to do next.
Is it possible to restore the phone to factory settings and after that try to recover the pictures? If it´s possible to restore it can someone give me some instruction on how to do it?
I will apriciate all the help from you guys.
Thanks
Click to expand...
Click to collapse
flash twrp, if your internal storage isnt encrypted then put a microsd card into your phone and copy your data.
Sent from my LG-K220 using XDA Labs
D1stRU3T0R said:
Hmm, if you have twrp dirty flash personas mod. If you don't, try t flash twrp, and after flash the mod. That won't delete your files, only make your phone to boot. Hopefully you had Android 6 already.
Click to expand...
Click to collapse
In the fastboot & rescue mode it the bottom it says in green "PHONE Locked". This might be a problem to flash ?
I run adb and my device is detected if I use "fastboot devices". When I try to run "fastboot flash recovery" it gives me the message below;
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26000 KB)...
OKAY [ 0.621s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
tcolaco said:
In the fastboot & rescue mode it the bottom it says in green "PHONE Locked". This might be a problem to flash ?
I run adb and my device is detected if I use "fastboot devices". When I try to run "fastboot flash recovery" it gives me the message below;
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (26000 KB)...
OKAY [ 0.621s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.627s
Click to expand...
Click to collapse
Unlock your bootloader... Get the unlock code, unlock it, and than repeat.
D1stRU3T0R said:
Unlock your bootloader... Get the unlock code, unlock it, and than repeat.
Click to expand...
Click to collapse
How do I get the codes ?? can you please clarify me.
Thanks
tcolaco said:
How do I get the codes ?? can you please clarify me.
Thanks
Click to expand...
Click to collapse
Search in the megathread and you will find it