Database Users

[Q] So, I messed up somewhere. *Recovery problems (I think)*

So, I lurked a couple different sites for android for a while. I just like to read the whats happening and such with tech, and I always read about root and how rooting pretty much makes a phone/tablet a whole different device, so today I rooted it (my Nexus 7)...
Well, I can't remember exactly what I did, because I have been searching every place on the internet to figure out exactly what I did and how to fix it.
Oh and I rooted it by manually doing it (with cmd and such)
When I try and get into recovery I get a android green dude laying down on his back with a red triangle with a ! in the middle that says "no command" below it. I have wiped and cleared cache. I have read a bit about this from searching the internet, but I have yet to find a way that works. I was thinking about trying to undo everything then reroot it, but I really no idea what to do. I did root it correctly (I believe), but I may have tried to update the recovery (maybe) and that may have done it. But like I said I can't remember what I did since it has been so long and I have read so much other stuff.
I can provide anymore info for anyone who wants to try and help.
Oh, I forgot to mention that I read that putting a new recovery on would probably take care of it, but when I try I get a message saying "installation aborted". How or why, I do not know.
Sorry, for rambling and the not too hot spelling and grammar. Been a while since I have posted on any forum.
I just keep forgetting things. I can still turn it on and do somethings. Things like the home softbutton/key (not sure what they are called) doesn't work, the notification bar only scrolls down on the one side, and no notifications show up there, I still have root according to the root checker app I used, so yeah.
Thanks.

The android dude lying on his back is the stock recovery.
Put your tablet in bootloader mode and
Code:
fastboot flash recovery name-of-your-custom-recovery-image-file.img
and proceed from there.
If you don't know what the above means you need to do some more reading - perhaps the fastboot/return to stock sticky thread.
PS: you should define what exactly you mean by "manually" as there are now two different rooting paths... my answer above presumes you rooted by unlocking the bootloader via fastboot. Up until recently, that was the most common method.

bftb0 said:
The android dude lying on his back is the stock recovery.
Put your tablet in bootloader mode and
Code:
fastboot flash recovery name-of-your-custom-recovery-image-file.img
and proceed from there.
If you don't know what the above means you need to do some more reading - perhaps the fastboot/return to stock sticky thread.
PS: you should define what exactly you mean by "manually" as there are now two different rooting paths... my answer above presumes you rooted by unlocking the bootloader via fastboot. Up until recently, that was the most common method.
Click to expand...
Click to collapse
OK.
I did that and I was able to get into clockwork, but I am still stuck with a non working home key and a notification bar that isn't working right. I think I would like to just go back to stock until I figure this out better, I thought I knew enough to root, but I guess I don't.
I did it that way (bootloader via fastboot). I just see people doing toolkits and stuff and I wanted to say I didn't use them, so people knew.
Thank you for the help.

Also, what sticky are you talking about? I'm not sure where it (the sticky) is located. If you could direct me to it or post a link, that would be awesome. I think I am going to hold off on the root. Just once I can get this back to stock.
Once again, thanks.

OK, I found the guide I used to help me along with rooting and I was going over it to redo the root, but during step 9 of it I got a problem.
C:\adt-bundle\sdk\platform-tools>fastboot flash recovery-clockwork-touch-6.0.3.1
-grouper.img
unknown partition 'recovery-clockwork-touch-6.0.3.1-grouper.img'
error: cannot determine image filename for 'recovery-clockwork-touch-6.0.3.1-gro
uper.img'
C:\adt-bundle\sdk\platform-tools>
I am actually getting 2 errors it appears:
C:\adt-bundle\sdk\platform-tools>fastboot flash recovery recovery-clockwork-6.0.
3.1-grouper
error: cannot load 'recovery-clockwork-6.0.3.1-grouper': No error
C:\adt-bundle\sdk\platform-tools>fastboot flash recovery recovery-clockwork-6.0.
3.1-grouper.img
error: cannot load 'recovery-clockwork-6.0.3.1-grouper.img': No error
C:\adt-bundle\sdk\platform-tools>
I can't post a link until I get 10 posts, so once I get 10, I will post it.

I found the guide to get back to stock, so I think I will try that.
[GUIDE] Flashing a Factory Image with fastboot / return to stock Is what I found and I will try.

During the erase userdata part, it seems it has gotten stuck.
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.18.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jdq39.zip
So, I stopped the stalled cmd and I started another to try and get the userdata erased.

So, I skipped the step to erase userdata and went on to the next one and I got this:
C:\adt-bundle\sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.
18.img
error: cannot load 'bootloader-grouper-4.18.img': No error
C:\adt-bundle\sdk\platform-tools>
I cannot seem to find a way around this error I have gotten a bunch of times.

All taken care of, someone over at Androidcentral helped me out.
So, thanks for the bit of help and this thread is done.

Welldang said:
All taken care of, someone over at Androidcentral helped me out.
So, thanks for the bit of help and this thread is done.
Click to expand...
Click to collapse
I would reccomend if you get any future issues use wugfresh nexus root toolkit.. I have used this many times to revert back to stock / full wipe or re root etc. Glad you sorted it dude. I hate it when something goes wrong but then learnng new stuff to do is always fun

I stepped out (it's the weekend!) so I just saw your posts now.
Congrats on getting it fixed.
The trouble you had with fastboot was that you did not use the correct number of arguments; the correct format is:
fastboot flash partition_name source_file
and you forgot to give the partition_name ("recovery")
In the future, I would recommend that you strictly avoid flashing the bootloader (not the "boot" partition, but the "bootloader" partition) unless it is absolutely, positively necessary. It is simply too dangerous - a mistake made here will cause a hard brick of your device.
cheers

Nexus 10 (Manta) Help Thread - Ask Your Questions Here!

Samsung/Google Nexus 10 Help Thread!
mantaray​
Welcome to the Nexus 10 help thread! You can ask all questions here without the need of background knowledge. This thread is dedicated to solve users problems, so if you don't want to start a new thread for your question, ask it here. Members ready to help will be monitoring this thread and provide answers as soon as possible. For a list of supporters, see here:
Current List of Supporters@demkantor - All Things Nexus - adb & fastboot expert!
@lj50036 - GitHub Expert and All Around Android Guy!
@rirozizo - Battery Guru and Android Know It All!
@XxLordxX - The Unbricker!​
Click to expand...
Click to collapse
Supporters: If you want to be put on or off the list, just send me a PM!
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @ like above. Also, if you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible for posting there, you may post here. And Please Read The 2nd & 3rd Post Of This Thread Before Posting! Thank you!
ROM developers: Please read this. Consider if you want to have a ROM specific help thread or not, if not, most likely questions about your ROM will be asked here if the users aren't eligible for posting in development section.
To all of you: Remember the Rules and the Forum Etiquette

Knowledge is Power!
This section is not meant to offend but rather inform XDA members, please read, understand and abide by what is said in this post... you will never be called a n00b if you do!
First Read This:
~~~~This alone will save you - thanks Tony Stark~~~~
How to post your problem or question
This isn't really complicated but the more you know the more likely you can find your own answer.
But we are here to help! So the more information you give us, the better/faster we may help you!
Step One
Have you searched for the answer to your problem/question?
If not do this first, both the search button in the XDA forums and Google work wonders.
At least attempt to show you did a little research before you scream help or this ROM is garbage, Not searching or just simply complaining will get you ignored EVEN IF YOU WRITE IN ALL CAPS
All questions belong in Q&A Forum All General Phone discussion in General NEVER post random problems in Developers section
Step Two
So you have searched for your answer and can't find it, that's okay, it happens to all of us. But before you create a new thread seek out a similar one (in the proper forum for you device) and ask there - or here.
You may think a new thread is better but in truth people look at the old ones just as much, and keeping all similar questions in one thread helps to elevate congestion and makes the next guys search a ton easier.
Step Three
Know what to post. This means explain your problem as best you can (dont write a book, just not "help my phone is possessed by demons" this is not helpful)
So this means explain all about your phone, boot into your bootloader and write down all from that screen within your post. Are you rooted? Explain where your troubles began and what you have tried to do to fix it.
Give details as much as possible, this often will include a logcat. Which there are many ways to get, learn how to before you have a problem.
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
Code:
cat /proc/last_kmsg
Also read THIS or maybe try THIS
Use pastebin or codewraps around your logcat ( # sign from above)
Obviously every problem and question will require different information, but the more you give the better chance someone can help you.
Step Four
Wait for your answer, do not post the same question in ten threads, one will do. While you are waiting keep searching for your own answer.
When someone gives you help say thank you (with the thanks button preferably - don't make a post that just says thanks... nope, never)
Even if you don't like the answer be grateful someone took time from their day to try and help, If you think it's bad advice maybe reiterate your question and politely ask for a clearer or better explanation to the solution.
Once you have an answer
Edit first post to add the fix. If there was no fix maybe explain why there is no fix in first post.
This will help others searching for a similar problem later. Make sure your helper was thanked as well.
*Remember ROMs, Kernels, etc, may be posted in the developer section, basic questions shouldn't be in those threads. If you must add something, like a bug report, be sure to add a logcat or you man not be helped.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Again, please understand that no one here is paid, we are here to learn and we help for fun. so please be respectful...

Quick Tips!
Okay, so if you look through the Q&A thread here the number one issue that keeps popping up is "Help Bootloop!" and "Help I Think it's Bricked!"
So here is a quick guide that will most often fix these issue (90% of the time anyway)
First things first.... Drivers
Now many of you have these installed, so if you can connect your device to PC through USB and are able to communicate with adb and fastboot just skip this.
If however you can not, then you need to download appropriate drivers for Windows.
You can get these through the Adroid SDK if you already have this
Or direct from the OEM following the link HERE
Or some say having the Naked Drivers works best, so try HERE or HERE or HERE
If you need help installing these then see the next chunk on adb/fastboot or feel free to ask here as well!
*Linux users just need the android rules set up, see fastboot link for how to...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So after drivers are up... Fastboot!
Well here is many's big fear, but fear not as the terminal is not that scary!
For an in depth explanation on how to use fastboot, I highly suggest reading through THIS
It will have all you need to know and if there are any further question please feel free to ask here or in the fastboot thread.
If you have any issues running fastboot (or adb) commands, please copy and paste all input/output from terminal/cmd here so one of your helpers can assist better.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can connect to PC and you know the commands.. but what to flash?
For the most part we want to use the stock firmware found here (some OTAs HERE for another use)
Download the latest for mantaray (currently 4.4.2-(KOT49H)
Now check MD5sum or sha1 for a match (Linux use terminal, windows use THIS)
If all is good lets extract the contents (I prefer 7zip but whatever)
So if all of your prep work is a success then when you type
Code:
fastboot devices
Into a terminal/CMD you will see your serial number
If not be sure you are in bootloader mode (power on while holding volume +)
Also have a high quality USB cable if not the one that came with your device
*Still have issue, ask in this thread!
If you have a locked bootloader it may be wise to
Code:
fastboot oem unlock
Then follow the below info, if you don't want to unlock your tablet just run the flash-all.bat to get similar results
And now you have a bunch of images, lets erase and flash so we will be oh so clean!
*have everything backed up first! this will erase your tablet!
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
now after we cleaned things up, lets flash back to stock!
Code:
fastboot flash bootloader nameofbootloader.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
(Everything should be named accordingly except for bootloader, so change this command)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Congrats! You can reboot to a functioning tablet!
Some quick notes:
If you want a custom recovery, fell free to instead flash latest TWRP or CWM or whatever.
You do not need to use stock recovery for the above to work, but you will need your custom recovery in a .img
Similarly if you want a custom ROM instead of stock you can do this, but only if your dev supplies you with the system.img, if not just boot to recovery, make a nandroid, wipe all, flash custom ROM and gapps through adb sideload.
If you still have a bootloop or a "brick" then ask us here and someone will be glad to give you personal assistance.
Or for real time help you can see if anyone is at ##Manta_Help_IRC on freenode
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Anything I missed feel free to ask in this thread!
Happy Flashing!

Tech Specs and More!
Want To Know More About Your Tablet
GENERAL INFO
GSM ARENA
Factory Images "mantaray" for Nexus 10
AOSP
Click to expand...
Click to collapse

Quick Linux/Unix Rooting Guide
First of all, you need to have Fastboot and ADB. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now follow the instructions on your tablet screen. As soon as your bootloader is unlocked the device will reboot, so you'll now download the recovery and the Superuser.
Get the TWRP from here (download the .img file): http://www.teamw.in/project/twrp2/128
Get the SuperSU from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
Click to expand...
Click to collapse
Copy SuperSU to your device internal memory (that's probably empty now) and rename the .img file of TWRP to recovery.img. Now enable USB debugging again (it's explained above lol) and replug the tablet on your PC. Time for typing again! (Please, open the terminal in the folder where the recovery.img is located).
Code:
adb reboot bootloader
Wait for it to reboot, and then type:
Code:
sudo fastboot boot recovery.img
(If you want to install the recovery permanently in the device, type 'sudo fastboot flash recovery recovery.img' before issuing the command above).
Now you probably see a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click in Install and select the SuperSU zip that you copied to your tablet internal memory earlier. When the flash is complete, reboot the tablet and congratulations! You're rooted :victory:.
Hope this helps anyone who may need it!
Click to expand...
Click to collapse
Quick Linux/Unix Restoring to Stock Guide
So you've decided that you don't want root anymore or you did something and want to restore to stock? That's not a hard thing to do! Just follow these steps and you'll be fine.
First you need to have adb and Fastboot ready. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now you'll follow the instructions on screen. When your device is unlocked, you'll have to download the stock firmware you want from one of those links:
Android 4.2.2. - https://dl.google.com/dl/android/aosp/mantaray-jdq39-factory-d79f489e.tgz
Android 4.3 - https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Android 4.4 - https://dl.google.com/dl/android/aosp/mantaray-krt16s-factory-94413961.tgz
Android 4.4.2 - https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz[/CODE]
Click to expand...
Click to collapse
Now that you're done with your download, you'll extract the .tgz package the way you prefer. Now, open a command line in the folder where the extracted files are and (with your device plugged on fastboot mode) just type:
Code:
chmod 755 flash-all.sh
sudo ./flash-all.sh
The procedure will now begin. It can take some time to finish. When it ends, it's recommended that you lock back your booloader, which is as easy as unlock. Type (tablet plugged in fastboot):
Code:
sudo fastboot oem lock
Hope this helps!
Click to expand...
Click to collapse
~Lord

XxLordxX said:
If you want I can do the Linux walkthrough and script . I'll be more than glad to assist in this.
~Lord
"This Story Ends Where It Began"
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
Yes a Linux walk-through is what I was going to do... I can also do a windows one it will just take me a bit longer... Thx lj

i want in! "all-round-android-guy"
Sent from my Nexus 4

Nexus 10
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110

kerriganinks said:
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110
Click to expand...
Click to collapse
What is your PC's OS.....:good:

OS
lj50036 said:
What is your PC's OS.....:good:
Click to expand...
Click to collapse
Windows 7 64 bit. on several machines. I tried 3 diff systems same results, even tried the hated toolkits, but the bootloader locks on any reboot at all. Negating any changes, the fastboot at least didn't reboot so it said all commands were completed, but nothing actually changed. I'm having issues reading those verifications on the page to post, is there a way around that. I got the phone number to call this in to Samsung for service, something has it locked and I've wasted way too much of my life toward trying to work on someone else's tablet. I've used the flash method on several phones and tablets in the past, so not a complete novice, just know it's not giving the same results as for others because something's wrong with the tablet.

This indeed is a strange issue, it seems others have had the same challenge
http://forum.xda-developers.com/showthread.php?t=2638227
Can you try the fastboot method of restoring stock again and this time copy and paste all input/output here
Also can you write down all info on bootloader screen
Sent from my Nexus 4 using XDA Premium 4 mobile app

Nexus 10 Boot behavior
Hello forum gurus!
I have a question regarding the boot behavior of the Nexus 10 that you'll probably know something about.
I need to have the device boot straight to the android desktop after it's been plugged in while in an off state. Usually, most devices boot into a battery-charging screen when you apply power while they're off, then they top up the battery and go to sleep, waiting for you to press the power button.
I'm hoping there is a way to alter this behavior and get the device to boot into android's desktop straight up. I've seen this setting being changed between different ROMs and I'd like to hear your opinion how to get the change done.
This is for a project of mine, the way I see it, i'll be using a few of these tablets for an installation.
Thank you for your feedback in advance!
Best,
Stef

Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app

Thanks a lot, also for the quick response.
I'll wait for your reply, so we don't end up pestering the same people twice for the same thing.
BR,W
demkantor said:
Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Please Help
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me

unitnerd said:
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me
Click to expand...
Click to collapse
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1

XxLordxX said:
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
How do i reformat with pc?

hi, i am very new to android (i still use a flip phone)
i have unlocked my nexus 10 (4.4.2), and have stopped there.
after the final steps in post #3
>fastboot erase system -w
>fastboot erase boot
>fastboot erase recovery
>fastboot flash bootloader nameofbootloader.img
>fastboot flash system system.img
>fastboot flash userdata userdata.img
>fastboot flash cache cache.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>Congrats! You can reboot to a functioning tablet!
after the reboot, would the device be rooted?
thanks in advance.

Not if using the factory image, you would still need to boot into recovery and flash superuser, then it would be rooted. Or boot to recovery and flash one of the many custom ROMs, all of which are prerooted
Really the only thing you need to do is unlock the bootloader, flash a custom recovery, then either flash a custom ROM or su
Sent from my Nexus 4 using XDA Premium 4 mobile app

thanks for the reply,
it looks like a 'catch 22' , but im sure its just that, i am seriously confused.
after reading several links, that link, to yet another linked guide.
i thought that i would use team win recovery project but it requires root. so thats a no go.
i checked a few others but same situation, require root to use.
could you/someone recomend a stable recovery or whatever i need.
...my head hurts, ill revisit this tomorrow.

[GUIDE] Return your European M8 to 100% Stock - S-OFF REQUIRED

*** I HAVE SOLD MY M8 BUT I WILL TRY AND KEEP THIS UP-TO-DATE WHEN NEW RUUs COME OUT ***
*** NEW GUIDE AS WE NOW HAVE AN RUU!!! ***
This guide is for Windows-only. The reason for this is because the htc_fastboot file used is a Windows binary and there doesn't appear to be a version for Mac/Linux
This guide will allow you to return your EU, unbranded M8_UL device to 100% stock (inc. locking the bootloader and removing the tampered flag) for resale purposes or to return to HTC. It does not cover carrier-branded handsets and does require you to be S-OFF but Step 3 can be done on an S-ON EU M8 so long as your bootloader is relocked and you match one of the CIDs listed below. A lot of this can be used to restore a US carrier M8 as the RUUs are available, though, but you'd have to get the relevant RUU.zip from the EXE (which is very easy)
This process applies to the following CIDs:
HTC__001
HTC__102
HTC__203
HTC__E11
HTC__405
HTC__Y13
HTC__304
HTC__A07
HTC__032
HTC__J15
HTC__016
HTC__M27
HTC__K18
HTC__A48
HTC__002
You need the following files stored in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (renamed to ruu.zip - not ruu.zip.zip!)
md5:4e03845aeab375746b4553e610047680
htc_fastboot.exe - *** REMOVED DUE TO HUGE AMMOUNTS OF SPAM REQUESTS ***
md5: 7343C5BCEC64373F83D69BD074954759
TWRP - http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.4.0-m8.img (renamed to recovery.img) md5:
e51c6ce8db0b7318ef31e1e7bd03c96e
And you'll also need HTC Sync Manager - http://www.htc.com/uk/support/software/htc-sync-manager.aspx (install it for the drivers and then uninstall it but leave the drivers on your PC)
All commands in bold are to be done in a command prompt window in your fastboot folder
1. 'Lock' the bootloader and reset the tamper flag
We know we can relock the bootloader by using the command 'fastboot oem lock', but it will show 'RELOCKED' on the bootloader and still show the phone has been unlocked in the past. With S-OFF we can set it back to 'LOCKED' . To do this, we need to use TWRP and adb shell
Flash TWRP in the usual manner by connecting the phone to the PC whilst in the bootloader and flash by using the command fastboot flash recovery recovery.img. Once flashed, boot the phone into TWRP and connect to your PC and make sure the drivers are successfully installed. To confirm it's working type adb devices and it should be listed with your devices serial number. Assuming you can see the device, we can now use adb shell to change the flag from 'UNLOCKED' to 'LOCKED' by using the following commands:
adb shell
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
Once the command has finished, we can continue using adb shell to reset the tamper flag by using the following command:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
Once this has finished, we can exit out of adb shell by simply typing exit. Then reboot the phone into the bootloader through the menu in TWRP so we can confirm the flags are set back to stock.
2. Change the CID (if required)
Now we're in the bootloader and are 'LOCKED' and not listed as modified (but still S-OFF) it's best we reset the CID so moving forward things are easy. To do this, you just need to use fastboot oem writecid HTC__001, or whichever CID your device originally came with from the list at the beginning of this guide. Once you've reset the CID, reboot the bootloader to confirm the changes using fastboot reboot-bootloader
3. Flash the RUU
We are now at the point where we can flash the RUU and restore the phone to 100% stock. To do this, we first need to boot the phone into RUU mode using the command fastboot oem rebootRUU. Once in RUU mode, you'll see a silver HTC logo on the phone and that's it. At this point, we now use the HTC fastboot package to flash their RUU.zip file using the command htc_fastboot flash zip ruu.zip. This process will take a few minutes, and the phone will reboot a few times but once done it'll say complete. At this point, reboot the phone back to the bootloader using fastboot reboot-bootloader
4. Factory reset the device *** OPTIONAL ***
Having flashed the RUU, I always prefer to do a factory reset to make sure everything is in order. To do this, boot into the stock recovery and once at the black screen hold volume up and press power to get into the menu and then select 'wipe data/factory reset' using the volume buttons and use power to select the option.
5. Reboot the phone
Pretty obvious this - just select 'reboot system now' and you should be good to go!

Reserved in case I need it

To adapt this for every single m8 would be incredibly simple, I'm not sure why you would target such a small group? Nice guide never the less.
Also you always need to flash firmware files twice.
Sent from my HTC One_M8 using xda app-developers app

exad said:
To adapt this for every single m8 would be incredibly simple, I'm not sure why you would target such a small group? Nice guide never the less.
Also you always need to flash firmware files twice.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Because there aren't any pre-packaged ZIPs for any other build - only Nandroids. Now, I'm sure someone could make a flashable ZIP out of a Nandroid but I don't have the time for that! Plus, you've then got to make sure the right FW package is available as well as the stock recovery. I also DIDN'T have to flash the FW package twice, it worked doing it once only but it does mention to do it again as a precaution
As I have an unbranded EU handset I did this guide - if anyone wants to use it as a template then please feel free to do so!

EddyOS said:
I also DIDN'T have to flash the FW package twice, it worked doing it once only but it does mention to do it again as a precaution
Click to expand...
Click to collapse
Any time hboot is flashed, you have to flash it twice for it to actually complete the full flash. There are no exceptions to the rule so if you did it once, you effectively didn't finish your firmware flash and run the risk of bricking your device instantly if you go S-ON to return it if the firmware was modified in any way over how it was stock. Please fix your guide before someone has modified their hboot to remove the red text and bricks their phone when they find the separate guide to go S-ON.

EtherealRemnant said:
Any time hboot is flashed, you have to flash it twice for it to actually complete the full flash. There are no exceptions to the rule so if you did it once, you effectively didn't finish your firmware flash and run the risk of bricking your device instantly if you go S-ON to return it if the firmware was modified in any way over how it was stock. Please fix your guide before someone has modified their hboot to remove the red text and bricks their phone when they find the separate guide to go S-ON.
Click to expand...
Click to collapse
It says it already!! I didn't flash it twice as I was already on the correct FW. I've made it bold so people will notice it
EddyOS said:
e. Type: fastboot flash zip firmware.zip and wait for process to complete. Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Click to expand...
Click to collapse

EddyOS said:
It says it already!! I didn't flash it twice as I was already on the correct FW
Click to expand...
Click to collapse
You're on the correct firmware but not everyone will be. Currently your guide sets people up for a brick should they follow it and then follow the procedure to go S-ON afterwards as many actually get rid of the red text. Its not optional to flash it twice like you make it sound, its mandatory. If you won't change the text, I'll report the thread because this will result in bricks, end of story.

EtherealRemnant said:
You're on the correct firmware but not everyone will be. Currently your guide sets people up for a brick should they follow it and then follow the procedure to go S-ON afterwards as many actually get rid of the red text. Its not optional to flash it twice like you make it sound, its mandatory. If you won't change the text, I'll report the thread because this will result in bricks, end of story.
Click to expand...
Click to collapse
In which case blame @mike1986. as it was taken from his firmware thread. I'll 'correct' it to please you but I don't agree with it as EU users will already be on the right FW. Nowhere does this mention that you have to go back to S-ON as that's nothing to do with this guide. All this is for is going back to stock

Text changed to make it a bit more obvious to do it twice, although this is different to flashing an RUU ZIP (where you HAVE to flash it twice as that's how the RUU ZIP works). Surely if it needed flashing twice it'd tell you to do it (as an RUU ZIP does)?

EddyOS said:
In which case blame @mike1986. as it was taken from his firmware thread. I'll 'correct' it to please you but I don't agree with it as EU users will already be on the right FW. Nowhere does this mention that you have to go back to S-ON as that's nothing to do with this guide. All this is for is going back to stock
Click to expand...
Click to collapse
I can't believe mike doesn't have it right either but I checked his thread and sure enough, there it is. Hopefully he'll change it since you tagged him here.
Even if you are on EU firmware, if you modify hboot to get rid of the red text and you have an incomplete firmware flash, you will brick if you turn the secure flag back on to return the device for warranty/exchange. Most people who return to stock are doing so in order to return the device so it is just smart to assume that they may have changed their hboot at some point.
EddyOS said:
Text changed to make it a bit more obvious to do it twice
Click to expand...
Click to collapse
Thank you.
EDIT: Noticed your edit to your post. It doesn't say something like this:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
After you do the first command? I suppose its possible HTC changed it. I don't have a firmware zip for me to go back to my T-Mobile firmware or I would try it myself to see but every HTC I've ever had before, if you are flashing an image with the hboot in it you had to do it twice. I wonder if the hboot is actually removed from mike's image.

EtherealRemnant said:
I can't believe mike doesn't have it right either but I checked his thread and sure enough, there it is. Hopefully he'll change it since you tagged him here.
Even if you are on EU firmware, if you modify hboot to get rid of the red text and you have an incomplete firmware flash, you will brick if you turn the secure flag back on to return the device for warranty/exchange. Most people who return to stock are doing so in order to return the device so it is just smart to assume that they may have changed their hboot at some point.
Thank you.
EDIT: Noticed your edit to your post. It doesn't say something like this:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
After you do the first command? I suppose its possible HTC changed it. I don't have a firmware zip for me to go back to my T-Mobile firmware or I would try it myself to see but every HTC I've ever had before, if you are flashing an image with the hboot in it you had to do it twice. I wonder if the hboot is actually removed from mike's image.
Click to expand...
Click to collapse
That's correct, it's not there any more. And the HBOOT is in the FW ZIP (see attached). That's why I didn't make it 'mandatory' as I assumed it wasn't needed as that warning didn't come up

EddyOS said:
That's correct, it's not there any more. And the HBOOT is in the FW ZIP (see attached). That's why I didn't make it 'mandatory' as I assumed it wasn't needed as that warning didn't come up
Click to expand...
Click to collapse
I still don't trust it and would continue to flash it twice to make sure. I don't remember the exact reason why the hboot caused it to fail all the time, something to do with the signature checking I believe.
The only way to really verify if it is actually flashing or not is to flash a different hboot this way and see if it actually works. I don't have the time to mess with it right now so I'd still suggest the old way. You know what they say about things that aren't broke...

EtherealRemnant said:
I still don't trust it and would continue to flash it twice to make sure. I don't remember the exact reason why the hboot caused it to fail all the time, something to do with the signature checking I believe.
The only way to really verify if it is actually flashing or not is to flash a different hboot this way and see if it actually works.
Click to expand...
Click to collapse
You're probably right, I just did what I did but then again I never flashed a custom HBOOT so it wasn't gonna be an issue (and I'd never go back to S-ON anyway)

EddyOS said:
You're probably right, I just did what I did but then again I never flashed a custom HBOOT so it wasn't gonna be an issue (and I'd never go back to S-ON anyway)
Click to expand...
Click to collapse
The only time I ever bother returning to stock is if I have to return the phone under warranty, sorry I was so mean about it, its just a serious issue when you have the potential to brick someone's device. I've never been unfortunate enough to brick but I've seen it posted before and what it came down to was something that wasn't explained clearly and could have been totally avoided. Thanks for the guide, I'm sure it will help many people. :good:

EtherealRemnant said:
The only time I ever bother returning to stock is if I have to return the phone under warranty, sorry I was so mean about it, its just a serious issue when you have the potential to brick someone's device. I've never been unfortunate enough to brick but I've seen it posted before and what it came down to was something that wasn't explained clearly and could have been totally avoided. Thanks for the guide, I'm sure it will help many people. :good:
Click to expand...
Click to collapse
It's all good! I've made one last change to that point to highlight that although it's not strictly required it's strongly recommended to do it twice as a precaution
Not sure what else you can out as no doubt someone will get it wrong at some point...

EddyOS said:
Not sure what else you can out as no doubt someone will get it wrong at some point...
Click to expand...
Click to collapse
It wouldn't be XDA if they didn't! :highfive:

Is it possible on my phone with CID HTC__J15 and S-on??

sari94 said:
Is it possible on my phone with CID HTC__J15 and S-on??
Click to expand...
Click to collapse
You can use parts of the guide but not the parts with (REQUIRES S-OFF) next to it (basically 1 and 5 are what you need, so long as you have an unbranded handset)

Added CIDs that will work with this guide to help users - if it's not listed then it won't work

Im guessing that once your back at stock you'll get OTA updates?

FIX HTC-U11☆corrupt☆relocked☆s-on☆

______________________________________________
REPAIR HTC U11 - CORRUPT - RELOCKED - S_ON
______________________________________________
I run a phone repair shop,
Customer brought a HTC U11 in to repair,
was soft bricked with an attempted custom rom installation then relocked the bootloader without flashing a working OS to it,
The os version was there but when the device booted a message appeared the device is corrupt cannot be trusted and will not boot,
this tutorial is how I managed to revive the dead device please read below.
Device specs on this model were :
______________________________________________
Fastboot oem readmid
2PZC10000
Fastboot oem readcid
htc_039
______________________________________________
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
_____________________________________________
Bootloader displayed killswitch enabled please disable,
Killswitch/frp
Killswitch/oem unlock
Killswitch/bootloader
when trying to unlock with provided original unlock_code.bin that was provided with the phone & returns not allowed on production build in bootloader, could not flash any stock recoveries or TWRP back to the device, also couldn't receive the unlock code
_____________________________________________
I used tried the following programs to flash :
•htc_fastboot.exe
•minimal adb and fastboot 1.7msi
•power shell on windows 8.1
•minimal adb & fastboot
•fastboot binaries from htc_dev.com
couldn't get anything to flash to the customers phone with any of these so dont bother.
____________________________________________
NOTE
I downloaded the OTA's & firmware from the google spreadsheet it had no file for the 2.33.710.9 section there the page it went to was 404 so I just downloaded all of the files with the same CID htc_039 in this case, so just download all relevant files with your matching CID main version shouldn't be an issue as it wasnt for me.
_____________________________________________
REPAIRING THE HTC U11
NOTE
☆Links are at the bottom of tutorial☆
#1 Go through the files in spreadsheet then download all with the same CID as you have even though the main versions might be different,
#2 try to flash them all with normal fastboot to see what is a signed or close to signed zip and what isnt, (you will know by the RUU errors you face anything but RUU security fail zip from USB command or RUU main version fail ) means it probably won't work but try anyway,
NOTE
I narrowed it down to a few but the one that did end up working was main version 1.11.710.5, but this main Verision was 2.33.710.9 ??? Dont ask me how it worked twice as it needed to be flushed first time it said but it did,
#4 Now the only flash tool that works for downloading to the device in RUU mode is the HTC 10 batch tool.
#5 Place the .zip into the "com" folder which is located where ever the batch tool is installed, in my case was C://Android/com
#6 Open the batch tool with administrator privledges,
select option 3 to open fastboot terminal with the purple screen
NOTE
when entered location of the terminal should be "example" C://android/com on the screen this is where you placed your RUU.zip file.
#7 boot U11 to download mode, with device off hold,
•Power
•Volume down
NOTE
plug the device into the computer & make sure drivers are installed properly and working.
#8 Type into the terminal "fastboot oem rebootRUU",
phone will reboot to RUU mode.
#9 type into terminal "fastboot flash zip <file_name.zip>
NOTE
do not add " " or < > into the command syntax simply drag and drop the file if you do not wish to type the entire filename out.
it flashed all 28 zips twice in my case as it needed to be flushed the first time, these same files would not work on any other fastboot terminal I would only ever receive RUU error zip from USB command or RUU error main version fail,
so there you go this helped me and now I hope it can help you all out with your broken U11 fix please enjoy and if this tutorial has helped you please dont forget to hit the thanks button
_____________________________________________
NOTES
when using the HTC 10 batch tool fastboot terminal you can use either standard "fastboot" syntax or the "htc_fastboot" syntax both work.
WINDOWS 10 USERS :
you MUST disable driver signature verification or you will not be able to install any drivers for your U11.
_____________________________________________
FASTBOOT COMMAND SYNTAX
_____________________________________________
STANDARD SYNTAX
fastboot oem rebootRUU
fastboot flash zip "<example.zip>"
HTC SYNTAX
htc_fastboot oem rebootRUU
htc_fastboot flash zip "<example.zip>"
_____________________________________________
LINKS
_____________________________________________
HTC 10 batch tool (credits to sneakyghost ),
http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
_____________________________________________
Google spreadsheet for your RUU (credits to 5m4r7ph0n36uru),
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
_____________________________________________
HTC drivers for your U11 (fastboot adb & mtp)
http://gsmusbdriverzone.xyz/download-htc-u11-usb-drivers-official.html
____________________________________________

☆☆☆EDIT☆☆☆
I have noticed in download mode OS VERSION is 2.33.710.9 still,
But in the OS system settings in about phone & also HTC sync manager the OS VERSION is 1.03.710.7,
BUT it can also receive and install OTA updates up until 1.29.710.9 version before it will not install any higher updates,
So may be best to unlock the bootloader & flash a newer RUU version to your device to OTA update.
Very strange indeed but just thought I'd better add it.
Thanks

Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Sent from my coconut frond hut using Tapatalk

mauiblue said:
Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Click to expand...
Click to collapse
Hey mate,
No problem at all
Firstly though I would strongly suggest to flash the Unlock_code.bin you got from HTC dev to unlock your bootloader while you have a functional OS,
enable OEM unlock in developer settings then flash unlock code via bootloader or download mode, will save you the big headache of what I was going through when the bootloader is re locked only signed firmware can be flashed but if unlocked can flash unsigned firmware to the device,
I'd say HTC has not repaired the device correctly at all, I'd be pursuing reimbursement for any money you have paid to them,
not even I have had re corruption or anything works like brand new just my OS version in download mode is 2.33.710.9 but zip I flashed in RUU mode was 1.03.710.7 but let me OTA all the way up to 1.29.710.9 before it stopped installing them it downloads it just wont install it,
I'd switch OEM unlock on, flash unlock_code.bin to get unlocked bootloader will stop you from getting the corruption error, I'd also change the OS also just to see if HTC havent flushed something out of the device properly.
Just please whatever you do do not lock the bootloader without a functional OS
Hope this helps mate, if you need any more help dont hesitate
Thanks

Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!

I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.

korom42 said:
Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!
Click to expand...
Click to collapse
No problem mate ,
I'm not sure why,
but the customer locked his bootloader before having a workable OS, he had a viper rom with TWRP on it & from what he told me he wanted the oreo bootloader and modem so tried to flash a firmware package that did not flash, but did not take a nandroid backup prior with TWRP then locked the bootloader allowing only signed firmware to be flashed, dont asky me why lol, as even re locking the bootloader it stills shows as modified in bootloader mode, possibly he thought that it would go away if he re locked it I cant be certain he wasnt to sure what he did,
I also had to re lock the bootloader after unlocking it to receive the OTA Updates from 1.03 - 1.29 as they wouldnt install they would download but not install as soon as I re locked it again I could OTA all the way up to 1.29.710.9 before the same would download but not install,
But in my personal reference to everyone you would be better of keeping the BL unlocked your device wont corrupt
As for the re lock of the bootloader snd the exact ruu version as mentioned in the post OS this was corrupted and would not boot, had no recovery only fastboot, download & RUU , could not flash token or receive unlock code, main version on device was showing version 2.33.710.9 as oreo firmware but ruu that I got to successfully flash with the HTC 10 batch tool was nougat 1.03.710.5, which was also giving me RUU error main version in normal and HTC fastboot but same file worked in the batch tool fastboot with or without htc-fastboot syntax I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would , main versions and SDK were both diff and it definitely works I recreated and flashed the device over and over again just to be sure before originally posting

mauiblue said:
I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.
Click to expand...
Click to collapse
Have to use fastboot to flash device, or sd card,
Fastboot is diff from adb, but glad everything is working well now for you mate and you shouldn't hopefully have anymore problems with it

Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse

mauiblue said:
Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse
Haha patience probably not lol I'm surprised the phone ever started working again after some of the things it got called , no I'm just persistent in everything I do if I cant repair it I make it my goal to repair it ,
That's what I explained to the customer also never lock a bootloader when they system doesn't function as it should only bad things can happen,
I kept getting the OTA notification pop up to but you cant turn it off on HTC like you can with Samsung
I just flashed oreo and kept BL unlocked and no problems again so far
But it does pay off to read that is very true, I learnt the hard way when I first started out with mobiles I had a brand new S3 when they just came out and ended up flashing an S2 kernel to it and literally burnt the touch controller out on the board and made the touch non functional, I've always read up on everything ever since before attempting repair modification or customisation and havent gone wrong since pretty much,
Speaking of HTC did they charge you a fee to supposedly "repair" your device, as I could tell just from what you mentioned something wasnt flushed right in it, which makes you entitled to a refund, I'd file a dispute with them for the work order and reimbursement on the postage and what not as to be honest I've even been all over HTC websites in aus and America and spoken to they're tech support also (usless might i add) even they state that sometimes they cannot even fix this exact issue, and they charge more for the fact the bootloader is modified to repair them,
Click to expand...
Click to collapse

Aloha M. Fortunately HTC has didn't charge me anything. The frustrating thing is that they didn't include with my phone documentation on what they supposedly had done to the phone. Obviously they were able to get the phone to boot up at least once. But it seems like they didn't even test the phone so that it would consistently boot up. Flashing the latest OS update wouldn't have taken much time. I really like HTC phones and their GUI but their customer service SUCKS donkey balls.
Aloha!
Sent from my HTC U11 using Tapatalk

Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.

mauiblue said:
Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.
Click to expand...
Click to collapse
That's great mate, glad it didnt cost you anything then, apart from the 5 week wait though that must have been terrible,
I would have thought they would package it up a bit better but then again they have never been good for service,
Anyhow everything must still be working well then and all issues seem to be gone, , I'm yet to receive a U12 into my work for repair but I do agree battery is pretty good on the U11 I can charge it and it last me 2 days almost before I have to charge it again, but then again I've had it open aswell and the battery takes up 3/4 of the phone under the hood it's a very big battery even in actual size,
Anymore problems with U11 or any other makes and models feel free to contact me through pm or post if you need help and I'll get back as soon as I can

Thanks Matty. All the best!
Sent from my HTC U11 using Tapatalk

So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas or advice would be appreciated.

RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
Hey mate,
Yeah somethings going wrong with your OS
What version of android is it using ? 7.0 or 8.0,
As the bootloader is unlocked please KEEP it unlocked dont relock it under any circumstances if relocked only a very specific version of firmware can be reflashed and if flash fail the device will be bricked completely until the correct RUU is flashed
S-ON shouldnt be a problem when BL is unlocked and you can flash most firmwares that match your HTC u11 MID & CID
Recovery should boot without an SD card so if say recovery is corrupted aswell as part of the system is also,
What you need to do is plug it into the PC and using fastboot type the command,
fastboot getvar mid
fastboot getvar cid
with the device in download mode if you can,
If it wont boot to download mode with the button combination
Turn USB debugging on & connect to pc now your going to be using adb
Type this command to try and reboot to download mode to use the fastboot command to obtain your device info
adb oem reboot-download
Or adb reboot-download
It should reboot you to download mode now where you can obtain the necessary info with the fastboot getvar command,
Once you have that info head over to the google spread sheet and download the firmwares that match your MID & CID and then use the tutorial one page 1 to flash the phone,
Remember do not lock BL under any circumstances bad things will happen if the flash goes wrong.

RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
I had an nearly similar problem with my SD Card it always was seen corrupt from the system even after formating the SD Card. Then I did a factory reset, that did the trick for me.
It may take some time to set up the phone again, but for me it was the only way to make it reusable again.
Try to use different hardkey combinations, there are more then one to get into bootloader or downloadmode and even with the ADB commands you can treat your device to do what you want!
I hope this will help you.

So the links that I posted don't work because I don't have enough posts. I have factory reset the phone a few times in an attempt to get things working properly again. Here's the info since I can't put up the screenshots:
Android version:
8.0.0
Security level:
June 1, 2018
Software:
Bad Boyz US unlocked U11 v3.8 (I have a feeling I may have used the wrong one here)
Kernel:
3.3.78-perf-gbd700a6
[email protected] #1
SMP PREEMPT
Baseband:
8998-002772-1712182056
Build:
2.42.617.7 9.0_g CL1011554

Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka

kajfux said:
Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
Click to expand...
Click to collapse
Have you tried the htc_fastboot command syntax mentioned in the tutorial also with the batch tool ? If so and its still not working Its 100% to do with the zip your trying to flash id say it contains header errors,
Has it given you an error somewhere along the lines of "
a terrible mishap happened with the original ret lens 0" thats another common error to receive to indicate that your .zip is no good,
Try another .zip that matches your PID & CID dont worry about the main version the htc batch tool fastboot command promt for bypasses bootloader security to allow rollback of the bootloader,
I successfully took mine back to nougat from oreo with a locked bootloader which couldnt be re unlocked due to all killswitches being on & S-ON, no recovery or working OS, only download, bootloader & RUU mode,
Deffo the .zip trust me sorry for the late reply aswell didnt get notification but i hope this helps you out a bit.

Hot Pepper Serrano HPP-L55B

Hi, sorry if this is the wrong place or wrong format. I want to share with others that I got treble_experimentations running on this phone.
I though this phone was the same as the Logic L55B which has a Unisoc SC9832E, but that seems to be wrong as it contains an MT6739 chipset. It took me a very long time to figure this out, and I didn't find any precise instructions online, despite the final steps not being complicated.
I got this phone very cheaply with the USA Lifeline Affordable Connectivity Program. It came stocked with advertisements and was very unresponsive and glitchy. So, it is gratifying to unlock it and install a community-maintained ROM, as it's possible many people are stuck with it.
I performed these steps. I do not know if they are all necessary
1. i enabled developer mode and OEM unlocking
2. on a system with mtkclient, i ran mtk e metadata,userdata,md_udc and mtk da seccfg unlock as documented at https://www.hovatek.com/forum/thread-40300.html . i did not need to install any kernel patches or anything. note: mtkclient can also be used to take factory images from the phone, or backup the super partition before flashing.
3. booted phone and ran adb reboot fastboot to get into user-space fastbootd mode. normal fastboot won't flash the logical system partition.
4. downloaded an arm32_binder64-ab image from https://github.com/phhusson/treble_experimentations/releases and extract with xz. i used v415 vanilla. edit: i recommend v414 as v415 was never stabilized. newer images are at https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-List
4b. Optional: If the image was larger than the vanilla image, then space needed to be freed. fastboot delete-logical-partition product accomplished this.
5. wiped old system image with fastboot erase system and flashed new with fastboot flash system imagename.img as documented at https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ . I did not need to touch the secure boot partition nor do anything extra.
6. performed mtk e userdata again to resolve occasional conflicts from booting the phone to reboot into fastbootd
The phone is now super snappy, no ads, very responsive, but of course with the vanilla image one must manually install any apps of interest.
It looks like flashing could also be done via the boot rom by working with the super partition.
It seems really helpful to try connecting phones to tools like mtkclient just in case they happen to speak the same protocol. Additionally there is a lot of information in adb shell getprop and a little in fastboot getvar all, but basically I spent the whole day persistently websearching, looking for similarities and possibilities, and trying things, until I found an avenue that worked.
With the some work contacting Hot Pepper, gpl kernel sources and such could be acquired.

fuzzyTew said:
Hi, sorry if this is the wrong place or wrong format. I want to share with others that I got treble_experimentations running on this phone.
I though this phone was the same as the Logic L55B which has a Unisoc SC9832E, but that seems to be wrong as it contains an MT6739 chipset. It took me a very long time to figure this out, and I didn't find any precise instructions online, despite the final steps not being complicated.
I got this phone very cheaply with the USA Lifeline Affordable Connectivity Program. It came stocked with advertisements and was very unresponsive and glitchy. So, it is gratifying to unlock it and install a community-maintained ROM, as it's possible many people are stuck with it.
I performed these steps. I do not know if they are all necessary
1. i enabled developer mode and OEM unlocking
2. on a system with mtkclient, i ran mtk e metadata,userdata,md_udc and mtk da seccfg unlock as documented at https://www.hovatek.com/forum/thread-40300.html . i did not need to install any kernel patches or anything. note: mtkclient can also be used to take factory images from the phone, or backup the super partition before flashing.
3. booted phone and ran adb reboot fastboot to get into user-space fastbootd mode. normal fastboot won't flash the logical system partition.
4. downloaded an arm32_binder64-ab image from https://github.com/phhusson/treble_experimentations/releases and extract with xz. i used v415 vanilla.
4b. Optional: If the image was larger than the vanilla image, then space needed to be freed. fastboot delete-logical-partition product accomplished this.
5. wiped old system image with fastboot erase system and flashed new with fastboot flash system imagename.img as documented at https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ . I did not need to touch the secure boot partition nor do anything extra.
6. performed mtk e userdata again to resolve occasional conflicts from booting the phone to reboot into fastbootd
The phone is now super snappy, no ads, very responsive, but of course with the vanilla image one must manually install any apps of interest.
It looks like flashing could also be done via the boot rom by working with the super partition.
It seems really helpful to try connecting phones to tools like mtkclient just in case they happen to speak the same protocol. Additionally there is a lot of information in adb shell getprop and a little in fastboot getvar all, but basically I spent the whole day persistently websearching, looking for similarities and possibilities, and trying things, until I found avenue that worked.
With the some work contacting Hot Pepper, gpl kernel sources and such could be acquired.
Click to expand...
Click to collapse
Yes, please continue this work, And if there are any other links Please let me know. Looking for info on the Scepter 8 tablet as well, That would be Awesome. Thank you for your time & efforts.

did you use either magisk or TWRP to flash? Do you know if any other system images are compatible or if uploading a UI theme is necessary? Is it still functional for you now? thnx

I searched for the Scepter 8 and found there is an existing thread covering that device, which also has information on working with Hot Pepper the corporation.
Zalg said:
did you use either magisk or TWRP to flash? Do you know if any other system images are compatible or if uploading a UI theme is necessary? Is it still functional for you now? thnx
Click to expand...
Click to collapse
As I mentioned in the first post, I used just mtkclient and fastboot to flash. I suspect TWRP could be made to work. I don't know much about magisk yet. mtkclient is at https://github.com/bkerler/mtkclient . In my opinion the mtkclient code does not sufficiently respect a principle called DRY to maintain it effectively, but at least it is open source and a normative project to communicate with mediatek firmware. mtkclient can be used to extract factory images or flash new partitions, among many other things.
mtkclient speaks a protocol that could possibly work from a phone as well as a desktop. the same is likely true of fastboot. i imagine people have not implemented that yet.
I suspect any treble-based image should work, but I don't really know as I'm new to these things. Making a non-treble image work could mean getting the GPL kernel sources from Hot Pepper which they are legally obligated to provide in their action of distributing a linux-based android phone in the USA.
I don't know what uploading a UI theme is; do other flashing processes require this? I didn't need to do this.
The phone is still working for me but has gotten much slower and glitchier after use; still not as bad as with the factory image, though. I haven't poked at its innards since I made the original post. I suspect it needs a treble_experimentations upgrade by now, or soon, as the revision I am running was a prerelease at the time.

@fuzzyTew, I'm following the same instructions, but mtkclient is giving me this output repeatedly:
I also don't know how to enter BROM mode. I looked at the guide you attached with no avail as the key combos don't work.
```
Port - Hint:
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
```
Any fixes?

Try the things in the output you pasted please. Thank you for trying the device setup.

fuzzyTew said:
Try the things in the output you pasted please. Thank you for trying the device setup.
Click to expand...
Click to collapse
I did, but it still isn't working. I'm also using a Chromebook that is using Crostini (linux) and the device doesn't get recognized at all. Probably a Chromebook issue tbh

The phone briefly offers a serial port when it is powered, which mtkclient looks for (the brief serial port should show up in dmesg kernel logs). You could also try running it as root.
You can also see if your device is recognised by an official Mediatek flasher if you find a version your system can run, or ask the communities around mtkclient.

It looks like Crostini doesn’t provide direct access to devices. You would need a system that does, or to poke a hole in the crostini container somehow, or to flash the phone a different way. As mentioned in the first post I found that way to enable fastboot from https://www.hovatek.com/forum/thread-40300.html after a lot of searching from my non-containerized linux system.

Ok. Yea, I probably would. Dang it that sucks. Ehh, I'm sure I'll get access to an actual PC or something that would actually work.

fuzzyTew said:
Hi, sorry if this is the wrong place or wrong format. I want to share with others that I got treble_experimentations running on this phone.
I though this phone was the same as the Logic L55B which has a Unisoc SC9832E, but that seems to be wrong as it contains an MT6739 chipset. It took me a very long time to figure this out, and I didn't find any precise instructions online, despite the final steps not being complicated.
I got this phone very cheaply with the USA Lifeline Affordable Connectivity Program. It came stocked with advertisements and was very unresponsive and glitchy. So, it is gratifying to unlock it and install a community-maintained ROM, as it's possible many people are stuck with it.
I performed these steps. I do not know if they are all necessary
1. i enabled developer mode and OEM unlocking
2. on a system with mtkclient, i ran mtk e metadata,userdata,md_udc and mtk da seccfg unlock as documented at https://www.hovatek.com/forum/thread-40300.html . i did not need to install any kernel patches or anything. note: mtkclient can also be used to take factory images from the phone, or backup the super partition before flashing.
3. booted phone and ran adb reboot fastboot to get into user-space fastbootd mode. normal fastboot won't flash the logical system partition.
4. downloaded an arm32_binder64-ab image from https://github.com/phhusson/treble_experimentations/releases and extract with xz. i used v415 vanilla. edit: i recommend v414 as v415 was never stabilized. newer images are at https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-List
4b. Optional: If the image was larger than the vanilla image, then space needed to be freed. fastboot delete-logical-partition product accomplished this.
5. wiped old system image with fastboot erase system and flashed new with fastboot flash system imagename.img as documented at https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ . I did not need to touch the secure boot partition nor do anything extra.
6. performed mtk e userdata again to resolve occasional conflicts from booting the phone to reboot into fastbootd
The phone is now super snappy, no ads, very responsive, but of course with the vanilla image one must manually install any apps of interest.
It looks like flashing could also be done via the boot rom by working with the super partition.
It seems really helpful to try connecting phones to tools like mtkclient just in case they happen to speak the same protocol. Additionally there is a lot of information in adb shell getprop and a little in fastboot getvar all, but basically I spent the whole day persistently websearching, looking for similarities and possibilities, and trying things, until I found an avenue that worked.
With the some work contacting Hot Pepper, gpl kernel sources and such could be acquired.
Click to expand...
Click to collapse
I have the followed the steps and everything seems like it went as described. But phone only boots to fastboot. For a brief second you see a screen popup but then goes black and to fastboot. Any ideas thanks in advance

Hello new to the forum I'm interested in flashing a custom ROM to my HP serrano pepper, looking for help getting started just now ran into this site look forward to learning more about the procedure