Related
Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
sobamaflyer said:
Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
Click to expand...
Click to collapse
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
krohnjw said:
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
Click to expand...
Click to collapse
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
sobamaflyer said:
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
Click to expand...
Click to collapse
Yeah, you have the stock recovery. You can't apply a new recovery through rom manager because the su binary doesn't have the appropriate permissions since the update.
Boot into the boot loader (Vol up and pwr). Don't go into recovery. Use fastboot from the boot loader to load CWM. Boot into CWM after flashed and flash the SU binary (mount /system first). After this boot up and delete/rename /etc/install-recovery.sh so that it won't overwrite CWM on each reboot. Install CWM again from Rom Manager or via fastboot (as it was overwritten on boot). Done.
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
sobamaflyer said:
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
Click to expand...
Click to collapse
Fastboot is merely a command line tool used for various operations on the device. Mainly though you'll use it to flash an image to a specific partition.
You'll need to boot the device into the boot loader (hold Vol up and power on).
Plug the device in via USB.
Open a command windows in the tools or platform-tools folder of the SDK (depending on your version of the SDK, where the fastboot.exe can be found) and issue the fasboot devices commmand. This should display the serial of any connected devices. If this comes back blank there is an issue with the installed driver. Reinstall the USB driver for the device using the supplied driver from an updated SDK.
Assuming fastboot devices shows one device you now can flash a recovery to the device. Download the appropriate recovery for your device (i9020(a), i9203 or NS 4G) http://mirror.sea.tdrevolution.net/cm/recoveries/. Place this file in the same directory for simplicity.
At this point you can flash your recovery.
fastboot flash recovery file.name.you.downloaded.img
If it is not in the same directory you can alternatively pass the full path to the image.
You now have a custom recovery installed. Select Recovery from the bootloader menu to now boot into this recovery.
Assuming you've already downloaded the su binary and it is on your SD card, mount /system from within CWM and then chose to install zip and select this from the SD card. You now have root access.
Now that a panic attack is settling...
I think I'm getting somewhere but not yet where I want to be. I go to Bootloader, I connect my USB and don't get anything different than above from my sdk tools menu (unusable cmd screen, fail showing on my phone). What does [eventually] work is going back to my "nexus S one click root" folder and clicking run.bat (as fastboot.exe and adb.exe in that folder also do the nothing).
This run.bat reads some sort of fail and boots my phone telling me that debugging is not checked (which it is) and takes me directly to there, then the cmd screen tells me to press enter when I've turned on the [already checked] usb debugging toggle.....what the hell I press enter. Now it goes into the old beautiful CWMR (3.0.xxxx) screen where I'm able to apply .zips, backup etc.
(luckily I think ahead and do a backup right this min.)
Then I go from that screen and decide to apply my new CM7.zip that started all this, I apply that and get a bootloop on the CM7 boot screen.......crap......I go clear my davlik and cache and install CM7 again. Same thing.....crap......
I try restoring my original backup from 9/5/11 I made right after first unlocking my phone.......CM7 bootloop screen.....dammmmiiiiit
I try restoring backup from 9/12 I made after getting everything just like I wanted it.......CM7 bootloop screen.......uh oh, panic beginning.
I restore the backup from a few lines ago, my phone comes back (thank god)
So:
-I have to have the right USB driver in my laptop because something from sdk ultimately talked to my phone?!
-Clockworkmod recovery 5.xxxx has never worked quite right for me, apparently 3.xxxx is still my magic answer?!
-Now that I've gotten this far should I try the same process to get back to my CWMR 3.xxxx screen and put some different files in my root to use than what I've done to this point?
....again, I apologize if I'm being myopic or asking dumb questions. I often say I only know just enough to be dangerous.
[SOLVED] - maybe/sort of
Between reading (and re-reading) the help above and continued research on my own I [think] I solved my problem.
I found the following 2 links:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
And basically started over from scratch, I deleted what I'd put in my pc and re-loaded using those instructions (in the right place, the right way). Doing this I was able to pull up a cmd window and this time it properly accessed my phone. I got it to fastboot recovery - load CWM 5.0... and from there got into my recovery menus on my phone this time.
One curious thing....I tried the part VI in "how to root the samsung" ...""stop the phone uninstalling the custom recovery image"...... I've tried several things there but still get an error that it is read only.
....I went on to install CM7, and it consequently updated right after to the latest CM7, At this moment I have full permissions, superuser access, was able to make a backup of yesterday, the CM7 this morning and then CM7.1.0.1 that loaded.
Will I ultimately have the same issue as before? But be able to overcome it in the same manner when I want to?
Thanks for the help
This is why one click methods are bad. When a problem arises you have no clue what to do because a software did it for you the first time. Glad you got it figured out.
Sent from my Nexus S 4G using xda premium
I I have been searching for the net how to root my gedified xoom wifi 4.1.2,
My main objectives are
a) Root my xoom (because it is needed for OCing, but if i can bypass this that would be better)
b) Overclock it to 1.5
I have found 1 way root my xoom but i am stuck. The instruction says open the xoom and press down to display "android recovery" after i press up to enter android recovery it show : Entering Android Recovery Mode Reading ODM fuse:1. BUT after that i get the lying android with a ! on his belly. then my xoom restarts.
Please help me overclock my xoom because when i play Chaos Rings it lags, and its really frustrating.
Up, can someone help me with this?
up
So the fact that you're GEDified, implies you have an unlocked bootloader.
So, Install a custom recovery, I'd recommend this one: http://forum.xda-developers.com/showthread.php?t=1235170
Then in recovery flash the zip file I have attached to root. credits to solarnz for making the zip file.
Yup i think i have a unlocked bootloader, can you give me a step by step instruction on how to install the custom recovery and flash with the zip file? (FYI: I'm a newbie in this kind of stuff)
One more thing this is my MAIN PROBLEM
I have found 1 way root my xoom but i am stuck. The instruction says open the xoom and press down to display "android recovery" after i press up to enter android recovery it show : Entering Android Recovery Mode Reading ODM fuse:1. BUT after that i get the lying android with a ! on his belly. then my xoom restarts.
thank you for the time.
matt4321 said:
So the fact that you're GEDified, implies you have an unlocked bootloader.
So, Install a custom recovery, I'd recommend this one: http://forum.xda-developers.com/showthread.php?t=1235170
Then in recovery flash the zip file I have attached to root. credits to solarnz for making the zip file.
Click to expand...
Click to collapse
scampupy said:
Yup i think i have a unlocked bootloader, can you give me a step by step instruction on how to install the custom recovery and flash with the zip file? (FYI: I'm a newbie in this kind of stuff)
One more thing this is my MAIN PROBLEM
I have found 1 way root my xoom but i am stuck. The instruction says open the xoom and press down to display "android recovery" after i press up to enter android recovery it show : Entering Android Recovery Mode Reading ODM fuse:1. BUT after that i get the lying android with a ! on his belly. then my xoom restarts.
thank you for the time.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/showthread.php?t=1468298
It's a really good, easy and simple GUI that can help install a custom recovery and more, the root function on it won't work though as I don't think it's been updated for jelly bean, but I may be wrong
yeah i think the root function wont work because i read the thread and the developer said he haven't tried it on jelly bean.Probably i'll just wait for his new update the 7heaven projekt. thanks for the help!:good:
matt4321 said:
Use this: http://forum.xda-developers.com/showthread.php?t=1468298
It's a really good, easy and simple GUI that can help install a custom recovery and more, the root function on it won't work though as I don't think it's been updated for jelly bean, but I may be wrong
Click to expand...
Click to collapse
Gedified xoom
I've been trying to access recovery on my gedified xoom and ran into the same problem. Only when i got the sleeping android with the i on the belly, the xoom did not reboot. It was just stuck like that so I pressed power button + volume up button to exit and what do you know it went into the recovery mode. The xoom now says
Android system recovery <3e>
Use volume keys to highlight ; power button to select
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Stumbled upon this by accident so dont know if it will work for you but hope it helps.
Gedified xoom
alternatively try this
http://forum.xda-developers.com/showthread.php?t=1936534
so did anyone have a sure but EASY way to root the xoom in the stock 4.2.1 state?
I'm dealing with the same problem OP stated in the first post.
shilohdrummer said:
so did anyone have a sure but EASY way to root the xoom in the stock 4.2.1 state?
I'm dealing with the same problem OP stated in the first post.
Click to expand...
Click to collapse
Ok so I am in the process of doing this myself. I'm kind of doing this off my own back as I cannot get the AIO tools etc to work, but there is a nice way of gaining root on 4.1.2.
So, assuming you have an unlocked bootloader and a PC on Windows do the following:
1) Download the root zip attached above in this thread.
2) Download the latest version with install scripts from here : http://forum.xda-developers.com/showthread.php?t=1782235
3) Put the root zip onto the external SD Card
4) Run the RUNME file
5) Use option 2 to boot into fastboot
6) Once fastboot is loaded use option 1
7) This will then install the recovery.
8) Power + volume up to reboot
9) Do not let the device boot into android, it will get rid of the new recovery menu, hold power (on the Motorola dual core splash) and get the device to turn off before android starts loading.
10) Once the Xoom is off, start it again, pressing the volume down key rapidly until you see some options at the top, select recovery, press volume up.
11) Welcome to your new recovery! So, we need to install the root update. So select install zip.
12) Choose the root zip, go through the options and install it.
13) Reboot your device
14) Check for SuperSU
Congratulations, you should now have root on your 4.1.2 GED'ed Xoom MZ604
Going put this in a fresh thread I think for any other self proclaimed noobs in my position
ratykat
shilohdrummer said:
so did anyone have a sure but EASY way to root the xoom in the stock 4.2.1 state?
I'm dealing with the same problem OP stated in the first post.
Click to expand...
Click to collapse
Same here... this is driving me mad... everything people describe in other posts just aint happening on my GED wifi Xoom!!
Please explain.......
1) Download the root zip attached above in this thread. -------- where?
2) Download the latest version with install scripts from here : http://forum.xda-developers.com/show....php?t=1782235 Which file??????
Here is how I rooted my xoom.
follow the directions here but instead of doing step 1 follow this for adb install http://www.support-4-you.com/main/i...ged-adb-installation&catid=40:how-tos&Itemid= it is a 1 click adb install then follow from step 2 on.
When you are done there you can install TWRP 2.4 touch screen recovery (a much better recovery than what you used to root.)
Download TWRP2.4 zip and put on the root of your external sd card. ( if you don't have a sd card we will do it another way just let me know)
Boot into recovery by turning your xoom off.
1. press power
2. when the moto dual core logo comes on wait 3 seconds and press volume down
3. recovery should be displayed across the top press volume up.
You can skip steps 1- 3 now that you are rooted if you download Quick Boot open it, select recovery and the grant Super user permission
4. go to install zip from sd card (just like when you rooted) and find the TWRP 2.4 Zip and install
5. reboot your xoom
6. you now have TWRP 2.4 recovery installed.
I tried to use the search and google but didn't really find anything helpful. Almost 2 years ago, I unlocked the bootloader back on honeycomb and did custom recovery, root, and custom rom. Then a little while after ICS came out, I did the OTA update.
Today, I reset the xoom back to stock ICS and tried to unlock the bootloader again...thinking nothing of it. The process was taking a few minutes so I decided to get a snack and when I came back it was rebooting.
I assumed that it worked and continued to try and fastboot a recovery image. The recovery image installed and I did another reboot but was greeted with the android welcome screen. Anyways I went through the menus and then tried to enter recovery and it gave me an android laying on its back with and exclamation point above his open chest.
I hard rebooted and can still get into my device, but adb cannot seem to find my xoom anymore. I have tried it on a 64bit desktop and laptop with no luck.
Have I messed up? Or is there a simple fix that I am missing? Thanks in advance for any help!
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
dfib1 said:
Can you get into fastboot mode? The second time you unlocked did you have to go through the questions on your xoom again?
Click to expand...
Click to collapse
Yes, I can get into fastboot by holding the volume down key and the power button. That's fastboot, right?
Yes, I had to go through the menus the second time I unlocked.
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
dfib1 said:
sounds like the recovery you try to fastboot did not take or the rom was corrupt.. Which recovery was it? Do you want to be rooted and run a custom rom or completely stock? what xoom do you have(wifi, 3g, 4g)
Click to expand...
Click to collapse
I want to flash this ROM
http://forum.xda-developers.com/showthread.php?t=1997434
With whichever recovery is best. I tried flashing this recovery:
http://forum.xda-developers.com/showthread.php?t=1074979
I am on a 4G xoom on 4.0.4 but I don't use my data plan. I would like to be on a nice stable build of 4.2.
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Well I got through all of the steps, but when I try to boot I get stuck in a loop of the roms boot logo. Is it okay to flash a wingray rom over a stingray device?
I think it is fine just the 3g/4g won't work.
I can get you going again but you are going to be starting with a locked honeycomb device. You will then have to either let it update to ICS or JB or unlock, root, install custom recovery and flash a rom. What xoom do you have 3g or 4g?
dfib1 said:
Download your rom choice, gapps and put them on the root of your sd card. If they are already there skip this step
I like TWRP Recovery the best. Easy to use and lots of options.
download this Twrp 2.4 img to the folder you hve fastboot in
open a cmd prompt in that o that folder
type fastboot flash recovery TWRPv2.4.1.0.img
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
You should be in twrp 2.4
select backup/restore and backup your current system
select install and find your rom select asnd then swipe to flash
when done then select home
select install again and find the gapps package and install
when done select wipe dalvick/cache
when done select reboot
select system
you should be good to go.
Click to expand...
Click to collapse
Okay I restored it again but this time i did a factory reset and wipe dalvick before flashing the rom and gapps. It works! Thank you for your help!
However, could I ask how to root this thing?
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
dfib1 said:
since you have a custom recovery on it already and are unlocked.
Download this file Universal xoom root place it on the root of your sd card and flash it. Then reboot and try a root required app such as root checker
Click to expand...
Click to collapse
Thanks! Got it!
g;lad to hear it.
I have a Xoom WiFi on Android 4.1.2
I was trying to Unlock, Flash Recovery, Root and then Flash a Rom. I have Flashed on my phone a couple of times so I am a little familiar with the process.
I did the following:
1.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
2.
adb reboot bootloader
fastboot flash recovery "name of file".img. (the file i used was "recovery-clockwork-touch-6.0.3.1-wingray.img").
3.
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
This is where things go wrong.
Upon reboot,
I press down volume upon seeing the logo.
It then says Android Recovery.
I then press up volume.
then it says entering Android Recovery Mode
reading ODM Fuse:1
Then the Green Android man shows up with the red triangle.
It sits there for a while then boots into Android normally.
I have been searching for a solution since this morning. Everything I found about this has not helped.
Earlier in the day I did Flash a different Recovery so I think I have two. I installed the ROM manger app. It shows two installed.
ClockworkMod Recovery
Team Win Recovery Project (TWRP)
I am stuck as to what to do... Please help.
Thanks
Jim
jbfoster said:
I have a Xoom WiFi on Android 4.1.2
I was trying to Unlock, Flash Recovery, Root and then Flash a Rom. I have Flashed on my phone a couple of times so I am a little familiar with the process.
I did the following:
1.
adb reboot bootloader
fastboot oem unlock
fastboot reboot
2.
adb reboot bootloader
fastboot flash recovery "name of file".img. (the file i used was "recovery-clockwork-touch-6.0.3.1-wingray.img").
3.
Once you have verification on your device that this has been flashed, reboot your device by holding volume up + power.
Then 3 seconds after you see the Motorola logo, hit volume down. You should now see "Android Recovery" in the top left corner. Hit volume up to boot into recovery.
This is where things go wrong.
Upon reboot,
I press down volume upon seeing the logo.
It then says Android Recovery.
I then press up volume.
then it says entering Android Recovery Mode
reading ODM Fuse:1
Then the Green Android man shows up with the red triangle.
It sits there for a while then boots into Android normally.
I have been searching for a solution since this morning. Everything I found about this has not helped.
Earlier in the day I did Flash a different Recovery so I think I have two. I installed the ROM manger app. It shows two installed.
ClockworkMod Recovery
Team Win Recovery Project (TWRP)
I am stuck as to what to do... Please help.
Thanks
Jim
Click to expand...
Click to collapse
Please follow the Root Method mentioned in the 2nd Post of LAIOT thread . You can easily find it within the Development Forum , or my signature.
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
One of the files link is broken.
The requested URL /atftas/OEM/Motorola/XOOM/Xoom-Universal-Root.zip2 was not found on this server.
I have another problem.
Now I have two devices. If I unplug the Xoom it still finds emulator 5554. What is emulator 5554?
Thanks
Jim
I got around the emulator 5554 problem by using the -d option. I followed everything and all went fine. I installed the app Root Checker Basic but it says Sorry! this device does not have proper root access.
All steps completed with no errors.
I guess I'm stuck again.
Jim
I flashed back to stock. Did all the steps again and the same thing.
I tried several more times and it still would not work.
I went to another site and downloaded the root.zip and it worked this time. The root file on this site would not work for for some reason.
The Android man with the red triangle problem is also gone. Not sure what fixed it. I assume that it was because I flashed back to stock and used a different root.zip file.
Thanks for all the help
Jim
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.