Database Users

[Q] Xoom files doesnt change

Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this

wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day

You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?

If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?

Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?

okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.

Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .

okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now

I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?

[Q] another noob with a rooting issue

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
ok so i used this: themikmik dot com/showthread.php?11114-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
after using the HTCDEV to unlock.
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
i am stuck in between step 10 and 11.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
i downloaded su, root checker,and busy box. root checker says the phone is rooted. i know i need to get the h boot to a lower level inorder to do the unrevoked3 program.
tried flashing the recovery and says "cant open /sdcard/pc36img.zip (bad)"
made sure it wasn't zip.zip and it was so i fixed that and still wouldn't work.
the only thing i am not sure of is step 10 and wether i did it right :Once the misc partition has been updated, you can downgrade your Bootloader and HBOOT to a non-watermarked version rootable with unrevoked.
does the partition auto update or do i need to do something to make it update? i didn't see any option for this. eveything up to this point went exacty liek it should have so now i am lost. i have searched numerous forums and found similar problems but none that were exactly the same. and none of the solutions worked for me. i tried all the basics rebooting, etc and nothing. any info would be greatly appriciated.
the only other thing that i may have done wrong that i can tell is what file i am trying to make the pc36img. at the bottom of post # 1 it has 2 attachments listed as pc36img files those are the ones i am trying to use. when i try to click the hyperlinks thru the rest of the post i get an error message from that site thats says " This account's public links are generating too much traffic and have been temporarily disabled! " so i dont know if that site has the same zip files or i am completely using the wrong zip file.
sorry for the long winded post i know the noob video says make it brief but i figured the more info the better.
thank you.

sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
Click to expand...
Click to collapse
Oh brother was it!
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
Click to expand...
Click to collapse
Your S-On,so your not rooted.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
Click to expand...
Click to collapse
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.

Diablo67 said:
Oh brother was it!
Your S-On,so your not rooted.
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Click to expand...
Click to collapse
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App

when i check with root checker it says i am rooted and have su. maybe it just means unlocked? busy box also says rooted?
pc36img is in all caps.
thanks for the quick response!

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible

evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
Click to expand...
Click to collapse
Ok,thanks for clearing that up,serious dudes i hate giving the wrong info when trying to help someone and i don't mind admitting when i'm wrong,lol.Your never to smart or old to learn something new.
Sent from my Dell computer.

I can probably help here.
If all you want is to be rooted, then you are. There's no reason to do the rest, especially if you're out of warranty. Since you already have a custom recovery installed, you can feel free to flash a custom ROM, and not even worry about the rest of the process.
The Dropbox links thing should be fixed now. I had to move them all to 4shared.
As far as the misc partition flashing, as long as you didn't get any errors when in the command prompt/adb shell, then I'm sure it flashed successfully. The only way to tell is if the Froyo PC36IMG.zip flashes successfully without a "main version fail."
I can assure you the PC36IMG works, as I've used it many times myself. Did you confirm the md5? Is it possible your SD card got corrupted somehow? Those are the only reasons it wouldn't pick it up.

thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?

98tib said:
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
Click to expand...
Click to collapse
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .

Captain_Throwback said:
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Click to expand...
Click to collapse
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.

98tib said:
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
Click to expand...
Click to collapse
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.

This is what's cool about this forum a noob asking a question and you get 4 big time contributors helping out!
Sent from my PC36100 using xda premium

Captain_Throwback said:
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
Click to expand...
Click to collapse
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem

98tib said:
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
Click to expand...
Click to collapse
What kind of sd card are you using? You might want to try a different card, or reformat the stock card, if that's what you're using. That's the only other reason it wouldn't pick up the file, provided it's named correctly. And I assume you verified the md5 and it's good? And you're certain the file is on the root of the sd card as well? I cant think of anything else that could be causing the problem. Let me make sure my bootloader reads the file just to make sure.
EDIT: Scratch everything I said above. If your phone still says "unlocked" at the top of the bootloader, the misc partition wasn't updated successfully. Did you already complete that part, with no errors? You need to reconnect the device while booted up, with USB Debugging enabled, and run those commands from the command prompt from the folder with adb in it. Make sure you have the files "flash_image" (extracted from zip file) and "mtd-eng.img" (extracted from zip file) on the root of your sd card. If you're using Windows 7, run Command Prompt as an administrator. Let me know the output of those commands before continuing. If you got any errors on that part, that would be why you can't flash the Froyo ROM.
I saw you mentioned that in your OP, but I guess I didn't realize you skipped that part. That'a really the most important part of the process. It's the part right before the sentence you mention about the misc partition being downgraded. That last command flashes the mtd-eng.img file to the misc partition.

both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.

98tib said:
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
Click to expand...
Click to collapse
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".

Captain_Throwback said:
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Click to expand...
Click to collapse
thank you, you are my savior! its always the dumb things that you think you did right that you did wrong! lol. thank you again!

now i'm off to screw something else up!

One Click install TWRP Recovery, then root

I'm NOT responsible if you bork your tablet because you can't follow simple instructions!​
I've just made a simple batch file with adb, and the recovery file all in one zip for y'all.
Make sure you've unlocked your bootloader by following instructions HERE
1) Download Chainfires latest root and copy to Your Internal SD card on your tablet
2) Download and install DRIVERS
3) Download and extract nexus7_2013_recovery_A+.zip to a folder on your PC.
4) Open folder where you extranted nexus7_2013_recovery.zip
5) Make sure your tablet is powered on, and connected to the PC, then click on "Nexus7.bat" and follow instructions. (If your PC is installing drivers once it boots into fastboot, WAIT until the drivers are installed before clicking next!)
6) Be ready and hold volume up as the tablet will restart automatically, keep holding volume up until you reach the TWRP screen
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Enjoy!
BIG thanks to Chainfire for his root, and team win recovery project for their fast work on the recovery!
07/30/13 Updated SuperSu link to latest revision (ver 1.51).
07/29/13 Updated SuperSu link to latest revision (ver 1.50).
For those that couldn't find their azzes if a target was painted on it, here's a link to the video.
http://www.youtube.com/watch?feature=player_embedded&v=UpcTMTu-5Qc
I'm NOT responsible if you bork your tablet because you can't follow simple instructions!​

I got through the first 5 steps. However the tablet rebooted to the OS. At step 6 how do you reboot into recovery?

Ravynmagi said:
I got through the first 5 steps. However the tablet rebooted to the OS. At step 6 how do you reboot into recovery?
Click to expand...
Click to collapse
ADB reboot recovery

Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Edit - Didn't see you had a video. It didn't boot me into fastboot. I'm sure I did something wrong. Thanks again!!!

evodon84 said:
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Make sure you've unlocked your bootloader by following instructions HERE
1) Download Chainfires latest root and copy to SD card
2) Download and install DRIVERS
3) Download and extract nexus7_2013_recovery_A+.zip to a folder on your PC.
4) Open folder where you extranted nexus7_2013_recovery.zip
5) Power off your device.
6) Once powered down, hold Volume Down and Power. (this will boot you into fasboot)
7) Make sure your tablet is connected to the PC, then click on "Nexus7.bat" and follow instructions. (If your PC is installing drivers once it boots into fastboot, WAIT until the drivers are installed before clicking next!)
8) Be ready and hold volume up as the tablet will restart automatically, keep holding volume up until you reach the TWRP screen
9) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
10) when you reboot Superuser will be updated automatically by the Play Store
Click to expand...
Click to collapse
Umm thanks, but the bat file boots you into fastboot...watch the video

When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.

greenmky said:
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
Click to expand...
Click to collapse
Yes, you may want to create a folder in there for organizing all your flashable zips

greenmky said:
When you say copy chainfire's SU to the SD CARD you mean to the root of the directory you get when you connect via MTP, right? Where the Alarms/Download/Movies/Music etc directories are, right?
I see this syntax used a lot "copy to SD card" when there's not really an SD card, so it's a bit confusing (not just here). Especially since there's no obvious SDcard directory exposed when you connect via MTP to a PC.
Click to expand...
Click to collapse
Yes, your INTERNAL SD CARD

Thanks guys, I haven't done much rooting / flashing with devices without SD cards before. I used the Nexus 7 toolkit to root the old Nexus 7. Everything I rooted before that had a real SD card to dump zips on - wanted to make sure where TWRP could access.

Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.

evodon84 said:
Thank you very much for this, worked for me on the second try. Might I be so bold to suggest these changes to your steps to make them more clear? If not I will edit my post.
Edit - Didn't see you had a video. It didn't boot me into fastboot. I'm sure I did something wrong. Thanks again!!!
Click to expand...
Click to collapse
I'm ammending the video now to reflect your suggestion about booting right into recovery afterwards...thank you

Ravynmagi said:
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
Click to expand...
Click to collapse
What error message are you getting at the end of the flash, or does it say success...watch the screen as it's flashing.
I just ammended the video, follow along

Ravynmagi said:
Looks like I'm still stuck at step 6. After running ADB reboot recovery, the tablet reboots and I see the dead Android with the red triangle. So I'm guessing Recovery didn't get flashed right.
So I rebooted it again. Ran the Nexus7.bat. It boots to Fastboot okay, and seems to be successfully after pressing enter a couple times. But ADB reboot recovery results in the red triangle again.
Click to expand...
Click to collapse
Try going directly into recovery right after the batch file finished and restarts your device. I had the same problem if I let my device boot and then reboot into recovery.
ATGAdmin said:
I'm ammending the video now to reflect your suggestion about booting right into recovery afterwards...thank you
Click to expand...
Click to collapse
Cool, glad I could be of some small assistance.

Rooted just fine, thanks! Saved me typing some adb commands and such.

evodon84 said:
Try going directly into recovery right after the batch file finished and restarts your device. I had the same problem if I let my device boot and then reboot into recovery.
Click to expand...
Click to collapse
Yes, that was the problem. I started doing the steps manually and instead of letting it reboot after flashing the recovery.img, I went straight to Recovery from Fastboot and it worked fine. Thanks.

Ravynmagi said:
Yes, that was the problem. I started doing the steps manually and instead of letting it reboot after flashing the recovery.img, I went straight to Recovery from Fastboot and it worked fine. Thanks.
Click to expand...
Click to collapse
I dont know what happened but this did not work, I can still boot my device, but now I have no recovery installed. If I attempt to boot into recovery, i get the red triangle underneath it says *No command* I have tried to research the problem here but no luck in getting TWRP to flash.

Just curious why was this moved out of development? I'm glad I caught it yesterday before it was moved. All the past android devices I've owned have had their root instructions under a development forum here on XDA. I would have assumed since this device was so new the root instructions where not available yet. I admit it would have been my fault for not searching but as I said the precedence has been search the development forum for root guide. Just a thought, I know you moderators are obviously forum gurus..but I think a good portion of the community is used to finding them their. Even the OP thought it was the proper location.

samg77 said:
Just curious why was this moved out of development? I'm glad I caught it yesterday before it was moved. All the past android devices I've owned have had their root instructions under a development forum here on XDA. I would have assumed since this device was so new the root instructions where not available yet. I admit it would have been my fault for not searching but as I said the precedence has been search the development forum for root guide. Just a thought, I know you moderators are obviously forum gurus..but I think a good portion of the community is used to finding them their. Even the OP thought it was the proper location.
Click to expand...
Click to collapse
There's no telling why they do what they do. I don't question it anymore lol
Sent using XDA premium on my Nexus 7 (2) tablet.

ATGAdmin said:
There's no telling why they do what they do. I don't question it anymore lol
Sent using XDA premium on my Nexus 7 (2) tablet.
Click to expand...
Click to collapse
Well honestly I posted the question mainly to have an intellectual conversion regarding allowing this to be in development until a alternate root method is posted.I mean I am not an android developer but I am a systems engineer for twenty years (by this I'm just simply pointing out I am of above average technical skill) and simply because I've always my root method for the past ...I'd estimate about a dozen android models I've rooted found root under development. So some others might miss it too

samg77 said:
Well honestly I posted the question mainly to have an intellectual conversion regarding allowing this to be in development until a alternate root method is posted.I mean I am not an android developer but I am a systems engineer for twenty years (by this I'm just simply pointing out I am of above average technical skill) and simply because I've always my root method for the past ...I'd estimate about a dozen android models I've rooted found root under development. So some others might miss it too
Click to expand...
Click to collapse
You're preaching to the choir bro, I'm with ya.
Sent using XDA premium on my Nexus 7 (2) tablet.

Stuck in TWRP

Hello,
I try to experiment with my phone a lot. I think I overdone it today.
Had no GPS running CM10.2 and went back to stock rooted.
Had a message today there was an update (from Sprint). Installed.
The phone booted right to TWRP and keeps on booting there.
I tried to restore the CM10 back up with no luck, tried restoring stock back up with no luck.
Then I wiped everything clean. Still boots to TWRP.
I do have my backups on my PC.
I have no roms in the phone anymore so I cant flash anything.
Any suggestions?
Keep in mind I am fairly new to this. If I have to read up on something just point me to the right direction.
THANKS!
Dominik

This belongs in the Q&A section. Do you know how to use adb? Chances are that even sideloading a rom will not work. I had this issue not to long ago and I had to completely restore my device using lg flash tool. It just keeps rebooting into twrp? Try downloading a rom on your pc. Download the android sdk, navigate to platform-tools inside of the sdk folder, place the download rom inside this folder, hold down shift key and right click, select open command window here, open twrp on your phone and click advanced and hit adb sideload, type adb devices in the command window and it should list your device(you need your phones drivers first!), the type in cmd adb sideload (name of rom) without "()". it should push it to your phone.
If that method does not work you need to use the lg flash tool. download this to your pc: http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/Sprint+LS980/
look at the readme inside the folder and it will navigate you to the step by step instructions. Just make sure you use the Sprint files included in the link above and not the Verizon files. Steps are the same, files are not. It's very important.

dozol said:
Hello,
I try to experiment with my phone a lot. I think I overdone it today.
Had no GPS running CM10.2 and went back to stock rooted.
Had a message today there was an update (from Sprint). Installed.
The phone booted right to TWRP and keeps on booting there.
I tried to restore the CM10 back up with no luck, tried restoring stock back up with no luck.
Then I wiped everything clean. Still boots to TWRP.
I do have my backups on my PC.
I have no roms in the phone anymore so I cant flash anything.
Any suggestions?
Keep in mind I am fairly new to this. If I have to read up on something just point me to the right direction.
THANKS!
Dominik
Click to expand...
Click to collapse
1. Never flash an OTA on a phone that's been modified in any way.
2. Never post questions in development.
3. What typo said

phatmanxxl said:
1. Never flash an OTA on a phone that's been modified in any way.
2. Never post questions in development.
3. What typo said
Click to expand...
Click to collapse
Sorry, I will ask in the correct sub-forum.
Dominik

dozol said:
Sorry, I will ask in the correct sub-forum.
Dominik
Click to expand...
Click to collapse
its an easy fix. search the forums for a fix.

New update available for KIW-L24

Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.

vsriram92 said:
Honor released an update today for its KIW-L24
This will upgrade your system to KIW-L24C567B351 from any of the versions given below.
If you are in KIW-L24C567B331CUSTC567D003 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74510/f1/full/update.zip
If you are in KIW-L24C567B334 - Download the package from http://update.hicloud.com:8180/TDS/data/files/p3/s15/G79/g0/v74512/f1/full/update.zip
This update consists of latest January Google security patches and few important bug fixes for device.
Click to expand...
Click to collapse
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.

So nice of their support site to be down...

tomlogan1 said:
Thanks for the note, but either there is an issue with the update or the file got corrupted on the download. I flashed it and emui went through the update process, rebooted and then said my SD card was corrupt and to format it.
I have a 128GB card full of music TBU and saved ROMs that I did not want to lose. Went back via TWRP to previous and no damaged SD card and all is well.
Might have been the file was corrupted but just be caareful and always backup before you make any changes.
Click to expand...
Click to collapse
Instructions > https://forum.xda-developers.com/honor-5x/how-to/guide-force-installing-stock-ota-t3502874

What are the bug fixes???
Are there any new features???
I am currently on custom ROM and would like to know the answers to these questions to see if it's worth it to go back to stock rom

Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.

m0ndul said:
Hi, is there a full firmware package for this new version? Tried to upgrade and got soft-bricked and I don't know if it's safe to flash the full B331 package.
[EDiT]
Flashed the full B331, booted and applied the B351 update by powering off and pressing Vol+ & Vol -. After booting it still says B331 and my WiFi is dead.
Click to expand...
Click to collapse
So much miss information .. no one bothers to find the truth

Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.

animeme said:
Can I ask where/when/how you found these files? There seems to be nothing official available, nor will Huawei provide any information about any prospective update.
Click to expand...
Click to collapse
Link below or install the Huawei Firmware Finder form the Google Play Store and set it up to get OTA files in settings.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=kiw-l24

deleted

So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.

GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
What he said.
I'm hoping it's nothing more than a VoLTE update that LOS maintainers warn against anyway, if there's actually no one to further explain what it is

received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature

my kiwi-L24 got re-flashed today, it is weird that this B351 update is no longer available from B331's update check
searched on internet, there is news about "honor 5c" getting a B351 nougat update

This came up on one of the 5X's that I have. Updated and forgot to put back stock recovery. Don't be like me and forget to do that. Now it won't work properly and I can't get to start any apps to try and fix it. I can put back TWRP and wipe it, but I don't want to lose my data. I also have that problem now where it keeps telling that the SD card is corrupted. I backed up the data and scrubbed the card in the phone but it keeps coming back with the same thing.
If someone did an actual successful update properly (with stock recovery) then please update and say if everything is working. If not, I'm going to have to find some way to backup the data and then scrub it.
*EDIT*
I believe something like this happened to me before. I was on B151 and went to B331 with TWRP installed by accident. What happened was that the OS was still running EMUI 3.1 but the build was saying B331. After fighting with it (and community support) I managed to get it to B331 fully and EMUI 4.0 - since then and a few custom ROMs I'm back on B151 EMUI 3.1 due to stability. Games and some apps just didn't work on the new one. The second phone was on B331 fully though - then I made the same mistake and it went to B351. This time though, the phone seems screwed. No apps will load. I can get into settings and the file manager, but no Titanium Backup and no Flashify. Going to put back TWRP and try to flash GAPPS and see if it will help me get into Play Store. From there I'll try to reinstall Flashify and flash the ZIP of the update. Will post back once done.
*EDIT*
Well that didn't work. Even after going back and trying to root the device again - then checking the option for it to not detect the dirty flash - still didn't work. Kept complaining that stock apps are already present.
I'm going to try and get some files off the device, but keep having issues. Not sure why. May just have to scrub. Will update again.
*EDIT*
With TWRP on I used "ADB PULL" to get certain files from the root system which I couldn't access otherwise for some reason. Then copied the other things (photos and such) and will now be using the UPDATE.APP to get it working. For this I formatted the SD from within TWRP and created the DLOAD folder (with no caps - so that's dload - but I'm not sure if it matters) and will be copying the UPDATE.APP. Not sure which version yet, because there was some problem with one I had downloaded before. So I need to double-check and re-download.
*EDIT*
So I've successfully flashed the UPDATE.APP from the SD card (same one the phone was claiming is corrupted). Just for reference, here is the file information and hashes.
File Name: Honor 5X_Firmware_KIW-L24_Android 6.0.1_EMUI 4.0_C567D003_United States.zip
Size: 1762266487 bytes
ADLER32: 27cb0c31
CRC32: 1d9379b9
MD2: 6517c34dc9bac0cd8680e3c4fd09d8d9
MD4: 4a803765c0ed54cb5d6853a9f365cd3b
MD5: 04f60b067d546ad71f556e44a7934dc7
SHA1: 8d2718568ac6509a40c95e42857d400395eb88d2
SHA256: 82975923172b3800d3f09f76691f2a694ab98110e3f909084a02bd566448386f
SHA384: da53b58b8e20395595590fd0cec30e56fa6a62e638ec53e46a74ebf58d051fdd7576602019bd3130ca5c00cc432715a0
SHA512: 806e0e8969c293ca8b497a786699ee306352ad6ef434552f2d23decff8a5279c7fd605e046c13f11c2f87947f5a2bdf23d78fdec6263661e68f023fd72bf4381
RIPEMD128: 9d963e5d51c9df9554fa3422da84dd27
RIPEMD160: a1e5b8f08b65dd2bb08e04d62db270ad8f4cf51a
TIGER128: 66fb4e4e4ce11cb30626aea807355f83
TIGER160: 66fb4e4e4ce11cb30626aea807355f8345f1dd79
TIGER192: 66fb4e4e4ce11cb30626aea807355f8345f1dd79dbb39488
GOST: 93774537f6ca49d4406f9d3a0316d014e1e099b34fc1cd9b968dacc870700827
The file name may be different, but as long as you got the right one you should be OK. If you have issues when copied to an SD card - verify that the file on the SD card has the correct hashes. To make it faster use CRC32. For more surety, use MD5. You can get a tool like WinMD5 to check. It's free.
So now that it's done, I'm going to set it up as a new phone and wait to see if the update comes back on. If it does, I'll get it down and upload the B351 recovery. After that I'll need to remember that I have to put back the stock recovery before running any updates. Flashify FTW.
BTW - during the initial setup after connecting to wireless it came back with the update. Pics to follow.
Files will be uploaded here: https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
*EDIT*
So the files are uploading to the folder. The screenshot is attached. Had one issue where after the update I couldn't get back into the phone. Had to wipe/factory reset. I've used FASTBOOT BOOT TWRP.IMG to take the backups of the BOOT and RECOVERY. Hopefully one of the gurus can use that and give the IMG files. I'm going to try root and get FLASHIFY to backup the stock recovery and add to the folder.

khat17 said:
This came up on one of the 5X's that I have...............
Click to expand...
Click to collapse
I don't really like to do double replies, but I guess for ease of finding the info it's better this way. Unless a mod thinks differently and wants to merge all the info.
Google Drive Link With Files
https://drive.google.com/open?id=0BzqEmGyNP_v6aTZTZDN6bWo2ZEk
This contains TWRP backups of the recovery and boot images. There's also a file called KIW-L24-B351 which was created with Flashify. I assume you can add the IMG extension to it and flash as needed.
Basically I had this update run on another phone (my wife's) and it messed with the phone due to the recovery being TWRP and not stock. My fault - forgot to do that before handing the phone back to her. I believe it happened to me before but it never messed up the phone this way. Nothing would work except core apps like settings and the stock file manager. The Play Store wouldn't even open.
Anyways - back to factory with UPDATE.APP then run the automatic update from an OTA update on wireless, then FASTBOOT BOOT TWRP.IMG and capture the backups. Then flash SuperSU to get root. Then Flashify. Files are uploaded for your convenience.
Warning that during the initial OTA it took a while. And after it was done I couldn't get into the phone with the password. Had to factory wipe/reset again and setup again. Disable passwords just in case I guess. Hope this helps others - have fun.
No major differences. I haven't really used the stock OS6 but some things look a little different. Nothing major. Will see when she's using it if it lags or has improved memory and such. Not sure if I'll be able to test with apps that wouldn't run previously for me, but will see. Tested with TransDrone and it failed. Once SeedBox information is loaded it still crashes. Only happens on OS6 so I'm sticking with OS5 on mine. Does not happen with custom roms however (from what I recall - would have to check back).

Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.

raulpcamara said:
Hello every one,
I have the Honor 5X KIW-L24 rooted with TWRP, stock ROM.
I received this OTA update and saddly i pressed the update button. Now the phone is in TWRP loop.
What can I do please help. I already wipe cache and Dalvik, didnt work.
Click to expand...
Click to collapse
Follow this video if don't know how to flash back stock recovery through adb. Then take a look at those threads how to downgrade, here, here, here. Hope it helps.

bluesky299 said:
received this B351 update over B331, also did factory reset, GUI lag seems gone, not noticing new feature
Click to expand...
Click to collapse
Same here.
It had been too many months of the Honor 5X in the closet so i almost lost track what to do but what i did was revert all the way back to Stock ROM (had to flash an extracted/saved Recovery.IMG) and then do the UPDATE.APP from Dload complete and repeat on up to the current B351.
Of course lost Root but when ready can add that back too.
Yes the Honor 5X runs much smoother now than before plus that Battery Drain issue (Remember That?) where we had to dig deep to change 4 to 0 i think, well Battery Life is also greatly improved on mine.

GrimReaper24 said:
So did anyone ever take a wack at this? I've done a lot of googling and haven't been able to find anything official off the support site about this update so I was wondering if it was legit or not? I know how the update zip suppose to work and how to make it work. Just wondering if anyone used this.
Click to expand...
Click to collapse
I tried to update as the previous user did using TWRP and got the corrupted SD card message. I then tried to go back to stock ROM. Went into bootloop.
Been having a hell of a time getting anything to work properly since.