G'day.
So, I got my motorola milestone and I followed the Milestone Root thread, which I followed and downloaded the required SBF files to flash the exploit recovery (so I can actually get root). However, when flashing, it will say "Erasing Flash Memory: 99%" and then it'll go "Uploading new data. 0%" and just hang on that. I pulled out the USB connection after about 15 minutes of it being stuck on it, and I didn't get a brick. Android still boots, but I'll possibly be without a recovery image for a little while!
Android is still booting. HOWEVER, I don't have any recovery image as it was successfully nuked by RSD Lite. The milestone will not flash the Exploit recovery, that's all!
So, I need some help.
Bootloader Version: 90.78
Firmware Version: 2.1-update1
Firmware Config Version: GAS_EMEA_USASHLS00RTINT_P016
Baseband Version: 3GSMEPU91A_U_91.07_56I
Baseband Config Version: UCASHLSMR2EMEAB1B806D.0R
Build Number: SHOLS_U2_02.36.0
Hi,
You know what, I got the exact same phone as yours and I spent hours trying to work it out, and I got mine rooted finally.
First of all, you can't downgrade your bootloader, but what you can do is to make your bootloader vulnerable.
You need to use a special vulnerable recovery that is made especially for 90.78
Google vulnerable_recovery_only_RAMDLD90_78 and use that file instead to downgrade the recovery.
Afterwards it's smooth sailing, but remember, afterwards, to enter recovery mode as our bootloader is 90.78, everytime the guide mentions up/camera button, just replace with hold x then power up until you get exclamation mark, then hold volume up, and press camera button.
Good luck
Thanks een625, I just fixed the problem. Thanks bro!
You can always find the latest vulnerable recovery sbf here:
android.doshaska.net/rootable
No worries mate... Glad I can help
een625 said:
Hi,
You know what, I got the exact same phone as yours and I spent hours trying to work it out, and I got mine rooted finally.
First of all, you can't downgrade your bootloader, but what you can do is to make your bootloader vulnerable.
You need to use a special vulnerable recovery that is made especially for 90.78
Google vulnerable_recovery_only_RAMDLD90_78 and use that file instead to downgrade the recovery.
Afterwards it's smooth sailing, but remember, afterwards, to enter recovery mode as our bootloader is 90.78, everytime the guide mentions up/camera button, just replace with hold x then power up until you get exclamation mark, then hold volume up, and press camera button.
Good luck
Click to expand...
Click to collapse
I have the same problem as the OP and did the procedure you detailed using the vulnerable_recovery_only_RAMDLD90_78 sbf on RSD, still no dice. I even tried the open recovery method which didn't work too and ended with the "E: EOCD Marker occurs after start of EOCD E: Signature verification failed" error.
After searching the forums all over the web, I see that I may have to apply a stock motorola sbf from the company site before the vulnerable recovery SBF, but reluctant to do it as I see that I will wipe everything and start afresh. I am not sure of which official SBF (service/non-service) to apply and the required version to allow rooting.
Need help!
Bootloader Version: 90.78
Firmware Version: 2.1-update1
Firmware Config Version: GAS_EMEA_USASHLS00RTINT_P016
Baseband Version: 3GSMEPU91A_U_91.07_56I
Baseband Config Version: UCASHLSMR2EMEAB1B806D.0R
Build Number: SHOLS_U2_02.36.0
Hi,
Can you tell me the steps you take one by one...
These are the steps I take:
h t t p://forum.xda-developers.com/showthread.php?t=696359
openrecovery is run AFTER you flash a vulnerable recovery on the device...
Remember on 90.78 the vulnerability is patched, which is why you need to make the 90.78 bootloader vulnerable again.
You can't downgrade it, the only thing to do is flash with the vulnerable version
Only after you flash it, you can run open recovery...
daxie:
Have you read the second point of "Possible issues you may encounter"?
here: http://android.doshaska.net/rootable
2. "E:EOCD marker occurs after start of EOCD E:signature verification failed" error after you apply the update.zip in recovery means that the vulnerable recovery has not been flashed successfully.
It seems that the key to successful recovery flash in some cases is to not let the phone to boot to android or recovery until the RSD Lite will signal PASS. When the RSD Lite is restarting the phone during flash, hold the D-Pad Up, so the phone enters the bootloader again immediately.
Click to expand...
Click to collapse
thanks guys, i finally did it, kabaldan's solution finally did it!
but have one final doubt, after i successfully rooted it, when i tried getting to Open Recovery (had the Open Recovery update.zip on the sd card root folder), I couldn't and I got the same "E:EOCD marker occurs after start of EOCD E:signature verification failed" error. What does this mean and does this mean that I am not completely rooted?
See the updated information about the recovery checking caused by OTA being applied in the past and how to avoid it:
http://android.doshaska.net/rootable
"E:EOCD marker occurs after start of EOCD E:signature verification failed" error after you apply the update.zip in recovery means that you do not have the vulnerable recovery on your phone.
If you applied an OTA update before, there is a script run at every system boot that checks and re-flashes the recovery when its checksum doesn't match. In such case, you have to avoid booting to android after the vulnerable recovery flash. Boot directly to recovery when RSD Lite restarts the phone (hold camera button) and from there remove the /system/etc/install-recovery.sh file.
rm -f /system/etc/install-recovery.sh
A script for OpenRecovery is attached (install OpenRecovery and put the script to /sdcard/OpenRecovery/scripts before you flash the vulnerable recovery). Later in OpenRecovery, the first thing you should do is to run this script from the Run Script menu.
Click to expand...
Click to collapse
kabaldan said:
See the updated information about the recovery checking caused by OTA being applied in the past and how to avoid it:
Click to expand...
Click to collapse
I just want to say: Nadlabak, you are a good guy I really appreciate your work
Sorry for OT.
Cheers!
Related
i have an unbranded black and red htc magic 32a with CM-4.0.4 pre-installed, but am struggling to update it.
recovery flasher says "backup failed", when I click the hidden bypass button and click Flash it says "flash failed".
all of the HTC magic rom updates from the official site say the rom is not for my device
attempting to do a factory reset restarts the phone but does nothing else
cyanogenmods updater says "you are running an old version of cyanogens roms. to use the updater, you have to upgrade manually...." i can't follow the link suggested because recovery flasher isn't working.
is there something i'm doing wrong?
your trying to flash a recovery... to an already rooted phone.. rather then a rom.. thats what your doing wrong.
Put rom on card, rename to update.zip
Turn off phone.
HOLD home button while pushing power to go to recovery..
When in recovery, depensing on which it is, you will see WIPE and FLASH UPDATE.
I hope you know what to do from there. Then look into updating your recovery through terminal.
So, today i did the following:
-rooted
-installed ClockworkMod Recovery v4.0.1.0
-downloaded the available OTA Update available (mine was still 1.18.)
-pressed install, the phone powered off, loaded the image with Android with the exclamation mark above it and it's been like that for about 45 minutes now... is that normal ? How long should it take to update ?
What do i do ?
I am afraid to press the power button as I fear it will brick it.
once you have this image with the exclamation mark in red, you have to press the power button + volume up.
now you have to choose to update from SD Card...
Ok, got it !
Now, it says "Cannot mount SDCARD:downloaded/OTA_Chacha_HTC_Europe_1.54.......Zip
Installation aborted."
I assume i must revert to Stock Recovery and then do it again, right ?
yep.
and to be sure, rename the file to "update.zip", since the recovery searches for this specific file name.
Which one should be renamed ?
Stockrecovery.zip or OTA_Chacha_HTC_Europe_1.54xxxxxxxxxx.zip ?
the OTA update.
Sorry for this but I'm stuck again.
I got the stockrecovery.zip from http://forum.xda-developers.com/showthread.php?t=1164468 but when I try to install it in CWM Recovery it says:
"E:Error in /sdcard/stockrecovery.zip
(Status 0)
Installation aborted."
What am I doing wrong ?
Isn't this the right Zip for me considering that I am trying to go back to Stock recovery for 1.18 and this one is for 1.33 ?
I just don't know how to flash to stock recovery ...
Ok, so I installed a clean 1.33 and after that I updated OTA 1.54.
But the way reverting to stock recovery is still a puzzle for me.
I tried with Terminal Emulator but it said that the file was not found on SDCARD.It was there, believe me.
I don't know, maybe someone will figure it out someday.
To revert to stock recovery you should rename the stock recovery to PH06IMG.zip.
The OTA update can be named whatever you like as you will select it manually, but the recovery has to be PH06IMG.zip. If you need any other infos you can hit me up on GTalk or Yahoo.
How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.
wierd165 said:
How do I revert back after one-click root to the stock everything including radio, rom, build, etc. I am currently running Cynagon mod RC1 7 and have had numerous issues, I would just like a clean, simple cut answer so I can give this to someone for the holidays, any help would be mightly appreciated, as i've asked this in the past and can never seem to get a clear cut answer, thanks.
Click to expand...
Click to collapse
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip
Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?
mahanddeem said:
Is this also working if you're coming from stock unrooted ICS 4.0.3 ?
And
Is there any risk of loosing IMEI if you're going full ROM ?
Click to expand...
Click to collapse
I have reverted back from 4.0.3 yesterday by reflashing the full 2.3.6 rom without any issues. I'm not sure I understand what you mean by losing IMEI.
My phone works just fine after doing this (more than once!).
pcbroch said:
Just flash a full rom, it should restore the radio, the recovery, and the OS. Then do a reset to factory defaults if you are paranoid.
Get the proper rom for you phone here:
http://forum.xda-developers.com/showthread.php?t=1063664
If you're on T-Mobile, you have an i9020-T, this should work for you. It is the full 2.3.6 image.
http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip
Click to expand...
Click to collapse
Ok here's my problem i did the ics update earlier before you told me this and still having issues, now when I go to recovery I get a android with his chest open with a red caution sign on it...how could I just format everything, essentially make it the way it was out of box so I could start over...because of all the issues I'm currently having.
When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.
OK thanks...Just please let's summarize this
1.You were on I9020T bone stock , unrooted
2.You had GB 2.3.6
3.You updated manually (or OTA) to 4.0.3
4.You decided to revert to GB 2.3.6
5.You used exactly the same method of manual update (stock recovery after copying the .zip file and in this case the full ROM of 2.3.6 to SD)
6.You followed the stock recovery steps and chose the .zip 2.3.6..
7.After everything was setup , you booted into GB 2.3.6 without any problems
Is that right ? or better if you make the exact detailed steps you did to revert to GB 2.3.6 would be apreciated
Thanks
furiannn said:
When you get to that point, you need to hold down power then press vol up. Then you will be able to flash the zip. You need to put the zip on the phone first though, unless you have CWM recovery, in which case you can mount the sdcard section and move it across then, and flash it after.
Click to expand...
Click to collapse
Tried, but then I get this error:
--Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: !less_than_int(1316544229. getprop("ro.build.date.utc"))
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
Any help?
I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App
Raver27 said:
I think u need a custom recovery to be able to revert back to gingerbread
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
how would I go about flashing the custom recovery? I tried to flash another full rom package with the recovery in it and like i said i got that error...
Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android
furiannn said:
Do you have a folder in windows where you have been flashing stuff from, using fastboot?
If so, just get this recovery image http://forum.xda-developers.com/showthread.php?t=988686
Download either the blue or green 5023 image. Doesnt matter which just changes colour of mod place the file in the same folder as the fastboot.
Next, with the phone off and after attaching the phone to USB, turn it on while pressing vol-up and power. You should see the boot option screen, the fastboot screen. Leave the phone there.
Now go back to cmd window in windows, and browse to the folder where you have all the fastboot files and where you have put the above image file. Then type in the following:
fastboot flash recovery <image name.img> (without the < >)
press enter and it'll flash the recovery and then you can install the old version of android
Click to expand...
Click to collapse
I don't believe I have a folder as such, being a person who is not familiar with the lingo, etc of all this i rooted it with one-click mod, and just flash things through this, are you saying I can flash things externally? sorry to sound like a bum, but i'm trying to understand thanks.
No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom
furiannn said:
No problem, we're all noobs once, hell i still am and only just coming to terms with it all! Just need to do a bit of researching, but heres the basics...
fastboot lets you flash stuff to the phone from windows, when the phone is attached to the USB and is in fastboot mode (just turned on, from vol-up/pwr).
Can unlock the boot loader and flash recovery images from there. Once thats done, most other stuff can be done from within the new recovery mode, clockworkmod being the one that everyone uses.
over at nexusshacks it's explained really well how to root your phone. And he provides a zip with everything you could want. That zip is the folder I was talking about in the last post. It comes with drivers to install when you first plug the USB in and the PC recognises the phone. Download the pack, install them drivers and then go back to my last post and take it from there
http://downloadandroidrom.com/file/NexusS/rooting/nexussrootnew.zip
EDIT: Also do a full wipe/data reset just before you flash the new rom
Click to expand...
Click to collapse
I'm using clockwork right now, but it seems to be corrupted, im running 4.0.3 right now on a full rom package, so your saying I should still do this? I think i may have done all that before, as the phone is rooted, but I used the one-click method instead.
Just download that file and then you'll have what you need on your pc to do what i mentioned above. Plug the phone in and reflash the new recovery which will not harm it, and then you'll be able to stick gingerbread or ICS back on. You gotta try things out otherwise you'll not understand what is going on. I dont know of any one click thing that will let you go back to default as it was before. After it flashes the new recovery, scroll down to "recovery" on the screen and press the power button, dont restart the system.
In hindsight, while the one click methods are easy to use, theyre getting used by people that dont do the necessary research to learn about the rooting and flashing process. This means you end up skipping so much that you learn about the whole rooting and flashing proocess when doing it manually, which in turn means you have more trouble getting out of it if you want it back to the way it was! No offence intended here, but you just need to man up and do it! All will be well
hi guys, my photon q (unlocked bootloader) running on Jelly Bean can't root. I follow step by step from this . When I flash CWMrecovery I get "variable not supported" in the middle on my screen and then every into recovery there's triangle red (above android logo). I also can't find back-up and restore option in my recovery. And when I tried flash SuperSU via recovery I got this:
-- Install /sdcard/Root...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
So I used another method, I used motofail2go to get root. but the problem goes to this: Always exploit failed, already factory reset (wipe data/cache) and push volume up + button power but nothing (exploid failed again)
Any ideas guys?
First, if your bootloader is unlocked you do NOT need to do motofail2go or any of that other nonsense.
Second, I recommend you try searching before posting.
If you search for "variable not supported" there is a treasure trove of information.
Take this thread for example. Seems stock recovery is playing tricks on you, unfortunately. It is curable tho.
Edit - this guy solved it by using TWRP...
I wonder if there's some file that just needs to be removed before flashing recovery? I'm not sure, but give TWRP a shot. It will root the device for you as well
Yeah I got rooted, I suggest to prefer TWRP than CWM. big thanks guys
How to install TWRP with JB OTA running
Here is a step-by-step for anyone who stumbles here looking for an answer. I had to remember how I forced it through the first time, so I could install TWRP on my second PQ. GOO manager doesn't install TWRP, despite offering to. I believe this is due to JB.
1. Download TWRP recovery file & save to "platform-tools" folder
2. Start command prompt in platform-tools folder
3. ~type "adb reboot-bootloader" (phone will boot into bootloader)
4. ~type "fastboot flash recovery openrecovery-twrp-2.5.0.0-asanti_c.img" (when that is the name of the TWRP recovery file in platform tools)
5. unplug USB, push power button - phone will turn off
6. Hold "vol-up" button in and press power button, release "vol-up" when screen turns on, phone will boot TWRP.
7. NAND backup, Flash rom or other.
Do it in this exact order & it will work. (should)
Enjoy *****es!
Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Download the 70mb package for firmware downgrade and the latest marshmallow firmware from your regional huawei's website.
Extract the small package and put the .app file in a folder called dload on the SD card and insert it in your phone.
Boot by holding volume + volume - and pressing power, holding all 3 buttons until the phone vibrates.
The package will flash and afterwards you repeat the process, this time using an .app file from the full marshmallow firmware.
The 70mb package installs not matter how messed up your file system is, and makes your phone ready for the MM firmware. This process brings any brick back to life. Good luck.
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
menriquez said:
I too was trying to root my FRD-L04 and apparently used the wrong TWRP because now I get...
Code:
Unable to open ' ' to wipe crypto key
Unable to wipe Data
Unable to format to remove encryption
Failed to mount /data (invalid argument)
and I cant get the keyboard loaded so I can log into my wifi when I do a factory reset. I really have no idea how best to attack this...my phone is bricked I can get into TWRP 3.0.2.0 recovery, sideload, and fastboot (i think). I am currently downloading the stock ROM for my device and will try to sideload it.
I feel I need to fix the data issues thought before trying to load the ROM as I dont think my data partition is working at all now. Does anyone have any suggestions or a step-by-step guide on how to fix my bricked phone?
I've tried all sort of things today but no matter what, I cant get a keyboard working so I guess that means I'm screwed....
EDIT - my phone doesnt have a insertable SD card so I cant fix things the way the above poster suggests.
Click to expand...
Click to collapse
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
sysak said:
If you have nougat just flash the correct recovery from the twrp you already have. https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Click to expand...
Click to collapse
This is truly one of the worse phones I have ever had when it comes to root and such. My frustration over what, for a unbranded unlocked phone that *should* probably SHIP with root, this phone has and is putting me through is super high.
That being said...so I flashed the new 3.1.0.0 recovery. Before doing that, I had just tried to Unbrick the phone with flashing B162 image with 3.0.3.0...so now the phone is totally frozen in the "Your device has been unlocked and can't be trusted..." screen. Nothing I seem to do can get it out of this mode.
I want to install the rooted b378 boot.img file I just downloaded, but am unable to find the button commands to get the bootloader loaded. Does anyone have any suggestions in somehow trying to save the day with this damned phone?
much thanks in advance.
EDIT: So I got the phone in bootloader mode by pressing vol up/vol down/power and inserting the usb cable...i flashed the rooted boot.img and twrp 3.1.0.1 to both recovery and recovery2 and now i can get into recovery. I feel like I may actually have a chance now to fix this damn thing...
So can anyone point me in a direction where, from this point with the new recovery loaded and the modded boot image installed, where i can get this phone working?? ill use ANY ROM it dont really matter at this point...
Don't worry. It's really easy, once you know what to do, just realy easy to screw up if you don't. If your phone is a mess just roll back to android 6 using the procedure i described above. Once your phone works, update to nougat and install twrp and root following this guide: https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Same issue
Ramonator said:
Hi, after trying unlock my bootloader, I couldn't get into recovery mode without "Your phone cannot be trusted" getting stuck on my screen.
I re-locked the boot loader but now when I go into recovery it says "Data Partition is corrupted please format" then it asks me to connect to a wifi network which then just shows errors everytime the password comes up.
I tried to turn on USB Debugging to ADB sideload a firmware, but I can't because the phone has been resetted; if I try to enter a wifi password the keyboard doesnt show it's just the google voice (which doesn't work) with no options. If i skip the wifi option it just goes on the google login and gets stuck on "Checking Info".
Any solutions to the problem please?
EDIT: I just re-unlocked the bootloader and now its permanently stuck on "Your device cannot be trusted, booting now" regardless of what buttons I press during startup
EDIT 2: I fixed it, it was long and complicated but I got it to work, here's how.
1. When flashing TWRP, I realized I was flashing the TWRP for EMUI 4, so I flashed TWRP for EMUI 5. (Make sure Bootloader is unlocked)
First have all the adb/fastboot drivers, for windows shift + right click the folder and click "Open Command here"
Make sure the twrp img file is in the same folder as the adb folder.
On the honor 8 phone, if it is stuck like mine, turn the phone off and then hold Volume Down + Power Button until the download mode is on the screen
Type "fastboot flash recovery (twrpfilename).img"
Once it's done, turn it off and then hold power button + volume up AND volume down at once till TWRP comes on
(Continuously hold it, if the "Your Device cannot be trusted" screen comes on release)
2. (Make sure internal storage and data are backed up externally for this)
Reset system, data, cache/dalvik, and internal storage
3. Download Update.zip and the second .zip from a website on google, search Honor 8 Manual Nougat and click the link from smartstocknews (I can't post links) but do not follow the steps from that website, and also download GAPPS from open GAPPS. Make sure ARM64 is selected and not ARM as well as 7.0
4. After wiping, mount the Honor 8 by connecting it via USB to a computer, and press "Mount" on TWRP
Upload the both update.zip and update_data_full_hw_eu.zip and GAPPS ARM64 7.0 to internal or external storage
5. Exit mount and go to install, install the zips in this specific order and do not reboot in between
A) Update.zip
B) Update_data_full_hw_eu.zip
C) GAPPS.zip
6. Reboot after GAPPS is done (it might show already installed, if that's the case then it's alright, reboot anyways)
Click to expand...
Click to collapse
I pretty much have the same issue. No keyboard showing, just the stupid voice thing, and the Bootloader is Relocked. How did you get it fully unlocked. I can't get it. I guess let me get that resolved first (the bootloader) and I can try to go from there. Please help me.
UPDATE: Never mind I fixed it. I'm not really for sure how either but I think it mainly was just persistence.
Didn't work
Hello, so earlier today I tried to install RROS newest version in hope to get magisk/unrooting my phone because I'm addicted to snapchat and I rooted my phone with SuperSU earlier but didn't know u can't login to snapchat after that. It failed idk why, (I followed instructions very clearly and searched info from internet before doing that) causing me to brick my phone so when I booted it, it only showed black screen. After couple hours not finding way to get into twrp with my circumstances I managed to flash boot, recovery and system images, I tried to reboot and see what happens, (just in case, I kinda knew I didn't had ROM installed at the time, I also was hoping RROS to boot) nothing happened expect my phone got stuck in boot screen for booting EMUI, which was not installed obviously. Again after couple hours I stumbled to your post and managed to finally get myself into TWRP, I followed again ur instructions and everything was going fine, no erros, not anything. When Gapps was finished installing, I rebooted and again it just got stuck into booting screen. I did press and hold Power button, vol+, vol- and got myself into some kind of ROM installing screen, (hard to explain I don't exactly know what is name of it) and no it wasn't Huawei erecovery screen (Power button & Vol+ and no it didn't work me either saying that "getting package info failed") so in that ROM installing screen it just was stuck at 5% installing, and now I don't know what to do. My phone got locked again and I'm stuck at booting screen.
Note:
I don't have SD Card, should I get one and install stock rom?
Sorry for being kinda unclear but I'm tired it was 7 hours ago I got my phone bricked and have surfed on the web finding for answers ever since.
Also as you might notice, yes, I'm new to modding devices etc but still I'm not totally noob. Please help ASAP.
[SOLVED] So after hour of watching netflix as depressed teen I tried to reboot my phone again just in case, got stuck in booting screen. Then I held Power Button + Vol+ and got myself into EMUI stock recovery mode, I chose wipe cache partition and wipe data/factory reset, after that I rebooted my phone, it was stuck in booting screen for like 2 minutes but then it actually finished booting and now my phone is again functioning and god bless locked & unrooted.