Database Users

Semi-Bricked myTouch 4G

Alright I have a semi-bricked mytouch 4G. (a friend's phone) I followed the gfree guide and did the hboot flash and now I'm in a boot loop. I have the original boot screen loaded and I can get to the recovery menu. S is off so the phone is rooted. How do I get CWM on the phone so I can install a new ROM and kernel so I can unbrick this thing. With my verizon fascinate I have options to go from where I am stuck (Odin and .md5 files). Where do I go from here? Can somone give me a step by step without pointing me to a different forum? I have searched for more than a couple of hours and this is where I have found myself.

Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.

darinmc said:
Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.
Click to expand...
Click to collapse
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.

fsuagentsmith said:
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.
Click to expand...
Click to collapse
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.

neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
I get sending recovery failed... any help from there?

fsuagentsmith said:
I get sending recovery failed... any help from there?
Click to expand...
Click to collapse
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?

neidlinger said:
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?
Click to expand...
Click to collapse
yes, I see that

fsuagentsmith said:
yes, I see that
Click to expand...
Click to collapse
ok I changed it to that screen on the phone while trying to push the recovery image. It worked!!!

Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.

neidlinger said:
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Where is the reboot recovery option? As I said in original post I'm familiar with Samsung Galaxy and CWM not so much this phone.

fsuagentsmith said:
Where is the reboot recovery option?
Click to expand...
Click to collapse
are you in Recovery or in Hboot? what color is the screen? black or white?

neidlinger said:
Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.
Click to expand...
Click to collapse
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?

neidlinger said:
are you in Recovery or in Hboot? what color is the screen? black or white?
Click to expand...
Click to collapse
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?

fsuagentsmith said:
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?
Click to expand...
Click to collapse
Awesome!!! I see what you told me to do! When I select recovery this is CWM 3! Awesome. I will see where I can go from here. I still may have questions.

fsuagentsmith said:
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?
Click to expand...
Click to collapse
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.

neidlinger said:
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.
Click to expand...
Click to collapse
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.

fsuagentsmith said:
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.
Click to expand...
Click to collapse
glad to see you got it going.
just make sure to do nandroid backups prior to flashing any new Kernels and make sure they are compatible with AOSP 2.3 ROMs.

neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down

steb0ne said:
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down
Click to expand...
Click to collapse
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App

Nicgraner said:
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Well, I was rooted and had been running the leaked 2.3 stock rom. Decided I wanted to try CM7...and flashed it and it appeared to flash okay b/c I was able to boot up, but I couldn't get gapps to install, so I ended up trying to restore from my backup, and that failed, and I couldn't get back to CM recovery. So, I'm stuck in a constant boot loop.

[TF300TG][Guide] Flashing back the original stock ROM

Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Disclaimer:
By following this guide, you will have to issue commands that risk to damage (aka. brick) your tablet or at least void your warranty. I won't be responsible for any damage made to your device. You've been warned.
Click to expand...
Click to collapse
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
And there you have ! You are now back to stock ROM with fully working 3G

Thanks a lot for this, I found these instructions on Wolf's thread but wasnt sure it would work with our devices, Thanks for taking the first big step.
Questions.
1. Does this wipe your data?
2. Does CWM still work after?

AFAIK, this will wipe your data, remove CWM and uninstall root. Your device's bootloader will still stay unlocked though.
You will have to flash CWM back using this guide: http://forum.xda-developers.com/showthread.php?t=1668173

Hi, followed the steps but it didnt work for me
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796653 KB)...
OKAY [137.443s]
writing 'system'...
FAILED (remote: ()
finished. total time: 138.477s
The Tab shows
Failed to process command flash:system error(0x170003)
The progress bar is showing under the USB logo with 1% blue, after hold power down I'm back into Onyx Rom
Any Thoughts?

I had the same problem and I just issued the same command a second time and it worked just fine
Try to format your /system (under the mounts and storage option) from CWM and wipe data and cache.

2nd time a charm!
Worked fine the second time i ran the command,
Im back to stock again :good:
I will wait for a 3G friendly Rom before flashing again
Thanks for your help
---------- Post added at 05:59 PM ---------- Previous post was at 05:42 PM ----------
Auliyaa said:
AFAIK, this will wipe your data, remove CWM and uninstall root. Your device's bootloader will still stay unlocked though.
You will have to flash CWM back using this guide: http://forum.xda-developers.com/showthread.php?t=1668173
Click to expand...
Click to collapse
Yip Sends you back to total stock
Stock Recovery
Stock Rom
only thing that sticks is Unlocked Bootloader

Thanks a million. This worked for me as well after 2 tries. Saved my $400!

Thanks heaps for this
I ended up in trouble when I flashed the TF300T firmware by mistake. It kept freezing and rebooting on me after that little stuff up.
Anyhow before I did that I made a backup with CWM, and after I restored it my 3G was gone but everything else worked fine.
Manual updates were failed though and they still do. At least I have my 3G back :victory:
So this method would probably work for upgrading to .40 as well, but it means a complete datawipe!
I'm sure there are many of us in the same boat now. I guess we will just have to wait and hope that some kind person makes a recovery image for the TF300TG?

Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
I got a question, i had problems with the touch since the last update, so i want to go back to the original, so my question is to perform this do i have to have the bootloader unlocked?

Auliyaa said:
Hi everyone,
[*] Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Click to expand...
Click to collapse
Hi, any idea why i dont have this 'USB icon' ?? i have 'wipe data' and an android icon that performs a cold boot.

Any idea why this will seemingly flash fine, but go to bootloop when I fastboot -i 0x0b05 reboot the tab?

Don't work for me
Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
Hi, followed the steps but it didnt work for me too
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796581 KB)...
OKAY [129.964s]
writing 'system'...
FAILED (remote: (InvalidState))
finished. total time: 182.134s
The Tab shows
signature mismatch
Can you help me?

hy
i'm having a problem with my tf300t...when i turn it on it shows the asus logo and in the upper left it show device is unlocked...but i can't enter the menu showing rck and the other 3 icons...i really don't know what to do...
then there is another thing...tried to install driver...i get to the part where the tablet is visible, but with the vol up and reset with a pin...it then shuts down and if i try to power it up it dissapears from the device manager...also...if i don't turn it up, the driver can't be installed...i tried every method...please help...
can i retun it to the repair service this way or i will loose my waranty?
sorry if the spelling isn't correct...i don't speak english fluently
waiting a response...thanks in advance

Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
fastboot -i 0x0B05 flash system blob
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
Using
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
is a tad wrong. It works, but only by accident.
You should be using
fastboot -i 0x0B05 flash staging blob
Click to expand...
Click to collapse
The technical reason for why your command works, is because the nvidia bootloader writes files to the staging area before writing it to the partition you specify.
What essentially happens is:
Blob is written to staging
Blob is copied to system (meaning non-booting system)
On reboot, blob is "extracted" from staging and properly flashed.
Step 3 is what makes it work in the end, but you are causing an extra unneeded write to the flash (step 2 is not really needed) (In this case it works, but it potentially increases the risk of bricking)

thx didn´t know that. So all the howto´s are wrong

benoitvdh said:
Hi, followed the steps but it didnt work for me too
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796581 KB)...
OKAY [129.964s]
writing 'system'...
FAILED (remote: (InvalidState))
finished. total time: 182.134s
The Tab shows
signature mismatch
Can you help me?
Click to expand...
Click to collapse
Your probably running Jellybean, if so this HOWTO does'nt work.

Question: What exactly is supposed to happen? First I tried it and got the fail and did it a second time and it seemingly worked. In my command prompt it ended with
"writing 'system' ... OKAY"
and wasn't doing anything after that in the command prompt and on the tablet there was a full status bar so it looked like whatever it was doing it was finished? So I held the power button and I think it was a boot loop ... it just was the ASUS screen with the spinning circle. So I just did it again, failed the first time did it again and now I am where I left off. I guess I will wait a while and see if it says "SUCCESS" on my tablet? And if not I will put in the reboot command? (I probably should have tried that last time instead of holding the power button I forgot about the last couple lines of the guide )
EDIT: Or is it cuz I am flashing the wrong SKU? I didn't know what one my tablet is supposed to be ... its a cyanogenmod build so I don't think I cant find what the SKU is supposed to be. I went with US SKU because I live in the United States but I don't know if that's what it is
EDIT2: After waiting a while with no "SUCCESS" Windows said that adb.exe crashed or something. So I put in the reboot command but now it seems to be stuck on the ASUS loading screen again.

Blackdrag said:
Question: What exactly is supposed to happen? First I tried it and got the fail and did it a second time and it seemingly worked. In my command prompt it ended with
"writing 'system' ... OKAY"
and wasn't doing anything after that in the command prompt and on the tablet there was a full status bar so it looked like whatever it was doing it was finished? So I held the power button and I think it was a boot loop ... it just was the ASUS screen with the spinning circle. So I just did it again, failed the first time did it again and now I am where I left off. I guess I will wait a while and see if it says "SUCCESS" on my tablet? And if not I will put in the reboot command? (I probably should have tried that last time instead of holding the power button I forgot about the last couple lines of the guide )
EDIT: Or is it cuz I am flashing the wrong SKU? I didn't know what one my tablet is supposed to be ... its a cyanogenmod build so I don't think I cant find what the SKU is supposed to be. I went with US SKU because I live in the United States but I don't know if that's what it is
EDIT2: After waiting a while with no "SUCCESS" Windows said that adb.exe crashed or something. So I put in the reboot command but now it seems to be stuck on the ASUS loading screen again.
Click to expand...
Click to collapse
I have a WW TF300T and had no problem flashing a US version.. so its no SKU problem how long did you wait on the ASUS screen with the spinning circle? It took up to 5 mins for me! just wait a lil bit longer next time.. And there comes no "SUCCESS" on the tablet! only a blue bar that should be full after SUCCESS comes up in your Fastboot-COMMANDLINE.. the reboot with the fastboot reboot command from the first page..just give your tab a bit more time.. its like a babe. handle it with care :silly:

Success!
Hazaa! I can confirm that I managed to flash back to stock by flashing the blob to the staging partition. Like so many other, the first flash failed but the second time worked. I now have working 3G again!

0nyx7 said:
I have a WW TF300T and had no problem flashing a US version.. so its no SKU problem how long did you wait on the ASUS screen with the spinning circle? It took up to 5 mins for me! just wait a lil bit longer next time.. And there comes no "SUCCESS" on the tablet! only a blue bar that should be full after SUCCESS comes up in your Fastboot-COMMANDLINE.. the reboot with the fastboot reboot command from the first page..just give your tab a bit more time.. its like a babe. handle it with care :silly:
Click to expand...
Click to collapse
Thanks for the reply 0nyx7!
I had waited a while, maybe 10-20 minutes? But I don't remember entirely. I tried flashing the stock firmware a few times but eventually I just gave up. I didn't like the possibility that my tablet was bricked so I just aborted mission and decided to go back to cm10 where it was safe. I just looked up a post on how to flash Clockworkmod Recovery with fasboot and then flashed a cm10 nightly I already had on my internal storage. So all is good... Mostly.

Nexus 7 - Bricked, Need Help, should be fixable!!

Hello,
Got a Nexus 7 (Wi-Fi), it was running on a CM 4.2.2 custom rom, then I decided to flash the original rooted 4.3 rom + franco kernel, after then, all the problems started - it was restarting all the time, some of the apps were not working, so decided to move to CM 4.3 again. After flashing CM 4.3 (newest), I got stuck in a bootlopp with Google logo
What is working:
- I can boot into fastboot (bootloader) mode
- The device has an unlocked bootloader
- I can boot into recovery (STOCK ONE, custom one disappeared)
-PDAnet drivers installed, so I can use adb sideload function while I am in recovery (apply update using adb option) - no use probably
What is not working:
Tried toolkits, seems like fastboot drivers or mode is corrupted, when I plug the tab to the PC, it says malfunctioned or smth like that
So, what I can do to fix this?
P.S it is not under warranty

Managed to sort out fastboot drivers, any further steps?

Pomperis said:
Managed to sort out fastboot drivers, any further steps?
Click to expand...
Click to collapse
Hi, Pomperis...
Yes... fastboot flash the Jellybean 4.3 factory stock image (see my sig for download link).
Be aware though, you might have problems flashing the bootloader (v4.23).
Go here for instructions, should you encounter that problem.
Rgrds,
Ged.

GedBlake said:
Hi, Pomperis...
Yes... fastboot flash the Jellybean 4.3 factory stock image (see my sig for download link).
Be aware though, you might have problems flashing the bootloader (v4.23).
Go here for instructions, should you encounter that problem.
Rgrds,
Ged.
Click to expand...
Click to collapse
Okay,
Got the stock image
Unpacked everything to platform tools folder and swapped the original bootloader image with the custom one (as advised in the thread)
When I type fastboot devices - it seems like fastboot is al right as I get:
xxxxxxxxxxxx fastboot
However, when I try the following steps:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (No such device or address)
finished. total time: -0.000s
Same with other commands
Any ideas?

Pomperis said:
Okay,
Got the stock image
Unpacked everything to platform tools folder and swapped the original bootloader image with the custom one (as advised in the thread)
When I type fastboot devices - it seems like fastboot is al right as I get:
xxxxxxxxxxxx fastboot
However, when I try the following steps:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (No such device or address)
finished. total time: -0.000s
Same with other commands
Any ideas?
Click to expand...
Click to collapse
That's odd... you clearly have a viable fastboot connection (re: fastboot devices... by the way, for securities sake, you'd be advised not to publicly make known your unique device ID... type some random digits if you wish to illustrate your point).
What happens when you run flash-all.bat?
Rgrds,
Ged.

GedBlake said:
That's odd... you clearly have a viable fastboot connection (re: fastboot devices... by the way, for securities sake, you'd be advised not to publicly make known your unique device ID... type some random digits if you wish to illustrate your point).
What happens when you run flash-all.bat?
Rgrds,
Ged.
Click to expand...
Click to collapse
Got this badass sorted out
Just kept reconnecting it to various usb ports and typing the commands till they worked.. Probably my drivers and fastboot was temperamental Got various errors, but now, the tablet has powered on and seems like fully functioning
I will blag it on eBay for a hundred or trade it in in any Cheetham Hill shop lol
Thanks for the help, that tutorial really helped

Pomperis said:
Got this badass sorted out
Just kept reconnecting it to various usb ports and typing the commands till they worked.. Probably my drivers and fastboot was temperamental Got various errors, but now, the tablet has powered on and seems like fully functioning
I will blag it on eBay for a hundred or trade it in in any Cheetham Hill shop lol
Thanks for the help, that tutorial really helped
Click to expand...
Click to collapse
Great you got it sorted... it's always the same with tech; lots of sophisticated software, but often the problem just boils down to a bad USB cable connection, or as you say, some other temperamental aspect... usually hardware!
Hope you get a good price for it.
Rgrds,
Ged.

In dire need of help to root Huawei P8 Lite.

Hi all!
First of all, Im new here, sorry if this is in wrong section (please don't delete the thread, move it to other section if needed) and that this has been posted millions of times but Im in really really dire need of help, and people told me this is best place to come to!
So here it is, I've tried countless methods and read alot of threads all over internet and nothing seem to work for me. (All info is down below just read it )
I tried with ADB and Fastboot, but where I get stuck always is with that my phone, somehow rejects new recoveries (TWRP, CWM) (???). What I mean is that when I try to start phone in a custom recovery(either holding +-volume and power button , or volume + and power or volume - and power) I get nothing(I can get him into his own recovery, but only options are to reset, shutdown and update and recovery and that is from first holding -volume and power then from fastboot and rescue mode and then by holding +volume). I got him ONCE to recovery(or whatever/however that place is called) where I can wipe partition cache and dalvik , it just stays at Huawei logo.
I tried both with scripts and with manual way where I input commands in cmd. I've bricked my phone about 4-5 times , and I know how to unbrick it with ease. What I dont know is how to get phone to take a custom recovery. And yes, I have unlocked BootLoader and followed all and every step there was in each guide I found. I tried with the most hated method (KingRoot and other kinds) but nothing.
Info you might need:
-As stated, phone is p8 lite, with marshmallow 6.0. (ALE-L21C432B584)
-BootLoader unlocked.
-I have all necessary drivers installed and all permissions on my computer for drivers to work correctly.
-Kernel Version - 3.10.86-gd9a2b44
-Yes of course I have debugging enabled everytime.
Once again, methods I have tried:
-ADB and FlashBoot
-All kinds of programs through phone (Kingroot, Iroot, KingOroot etc.. (I read that you can't root phone through this method but gave it a shot.))
-I don't remember if there was any other method to do it tbh because Ive been doing it for last 2 days and Im kinda tired and super pissed hehe.
But if I forgot/missed something of information that you need please just ask.
Sorry if there is too much of detail, I just wanted to describe my problem as perfectly as possible and as in much detail as needed.
Thank you all who will read/read (Oh the typing world) my thread I really appreciate your time and effort. All and any help regarding my problem will be tried out and appreciated ^^!

What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.

keikari said:
What do you mean by "rejects new recoveries" what kind of error message it gives. And you can test to download Terminal Emulator app and type "reboot recovery" if you have TWRP correctly installed it will boot into it.
Click to expand...
Click to collapse
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.

Ebilog said:
I installed a twrp recovery many times and every time i start my phone to get into a recovery it doesnt want to do it , like its not there. It gives no error message it just doesnt do what its supposed to do.
I tried with terminal emulator but it says permission denied?
Edit: I reinstalled my sistem last night so I probably dont have custom recovery at all atm so terminal might not work I guess. But what I said Is what happend before.
Click to expand...
Click to collapse
Weird, though you must have done something wrong when installing TWRP, because it removes stock recovery. Make sure you have typed everything right. Because if you type like "flash recvery" insted of "flash recovery" it shows stuff that by quick glance might seem correct. Oh I forgot you need root to reboot with terminal emulator XD mb. Could you show what fastboot shows when you install TWRP.

Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?

Ebilog said:
Ill get on to in once im at pc and retry the process. Ill get back to you once im done with it. Following the mega rooting thread best idea?
Click to expand...
Click to collapse
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.

keikari said:
Yeah it seems good except there is newer version of TWRP which you can use here https://forum.xda-developers.com/p8lite/general/twrp-v3-1-0-cherry-kirin-620-t3572004.
Click to expand...
Click to collapse
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||

Ebilog said:
So yea i installed twrp recovery and when i press +volume and power phone , logo shows up and phone turns off :|
And i tried with "adb reboot recovery" command , same thing happens.
What does this mean ? I have bootloader unlocked. Whats stopping me ?
Edit: Forgot to say, phone wont turn on now. Gotta reinstall system again :||
Click to expand...
Click to collapse
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"

keikari said:
That's very weird. There shouldn't be anything that could prevent it to boot recovery after installation. Could you copy and paste what fastboot tells after "fastboot flash recovery twrp-3.1.0-0-cherry.img"
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP

Ebilog said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
W3D7N16628011860 device
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
W3D7N16628011860 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users\Zeus\Desktop\twrp-3.1.0-0-cherry.img
target reported max download size of 471859200 bytes
sending 'recovery' (25096 KB)...
OKAY [ 0.672s]
writing 'recovery'...
OKAY [ 2.382s]
finished. total time: 3.058s
Im sorry i know im a bit of a bother but could i pm you or something i rly wonna see if this is fixable or i cant do anything root related to my phone ? XP
Click to expand...
Click to collapse
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.

keikari said:
You can, but I have no idea whats wrong with your device. Though sometimes it can take like 30-60s for huawei logo to show until it goes to TWRP. This is realy weird, never heard anyone else having problem like this.
Click to expand...
Click to collapse
So i managed somehow to get the to twrp menu and i flashed supersu and i flashed new version of twrp . but i think thats what made it crash. Would it be ok if my phone stayed with 3.0.2.0 ver instead of getting 3.1.0.0?
Bcoz when i flashed 3.1.0.0 phone got stuck on 2nd logo and didnt reset or anything.
Thank god i know how to unbrick a phone at least hahahah
Edit: If this thread stays and people with problem like mine need help , feel free to pm me ill gladly help

yeah older TWRP is good if it works.
Though problems you got are still weird.

I had this problem ..
If you have restored your system and can access twrp recovery , download supersu v2.62 and install it .. this version worked for me after trying many ..
Every time my phone bricks i was downloading new whole system , instead try flashing it with twrp its better ..
Good luck .

Safe to reboot? axon7toolkit boot.img remote: unknown command

Hey everyone,
I am in the process of rooting my axon7 (B10) and need some quick advice
I unlocked the bootloader using this method: https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595
Then went on to install twrp using the axon7toolkit. steps 1 and 2 reported to be working correctly but during the twrp install this came up. (see attached)
okay so recovery flashed successfully, but something went wrong with reboot? why, how, there is no indication that the tool wrote anything to boot.img so I should be fine? Can I just boot to recovery manually and continue normally? Or should I be worried that something went wrong?
the phone is currently still in fastboot mode and responding. however I am super cautious and don't want to brick the phone because I didn't ask so I am keeping it in this state for now.
any help is much appreciated
Checking ADB\Fastboot Connectivity...
ADB device connected!
Rebooting to bootloader...
Checking Fastboot Connectivity...
Fastboot device connected!
Flashing TWRP...
target reported max download size of 536870912 bytes
sending 'recovery' (14452 KB)...
OKAY [ 0.484s]
writing 'recovery'...
OKAY [ 0.113s]
finished. total time: 0.601s
Booting TWRP...
downloading 'boot.img'...
OKAY [ 0.475s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.497s
Tap 'Keep read-only'" on startup!
Checking ADB Recovery Connectivity...
Checking ADB Recovery Connectivity...
Click to expand...
Click to collapse

fleity said:
Hey everyone,
I am in the process of rooting my axon7 (B10) and need some quick advice
I unlocked the bootloader using this method: https://forum.xda-developers.com/axon-7/how-to/guide-unlock-bootloader-easily-t3704595
Then went on to install twrp using the axon7toolkit. steps 1 and 2 reported to be working correctly but during the twrp install this came up. (see attached)
okay so recovery flashed successfully, but something went wrong with reboot? why, how, there is no indication that the tool wrote anything to boot.img so I should be fine? Can I just boot to recovery manually and continue normally? Or should I be worried that something went wrong?
the phone is currently still in fastboot mode and responding. however I am super cautious and don't want to brick the phone because I didn't ask so I am keeping it in this state for now.
any help is much appreciated
Click to expand...
Click to collapse
Why do you even use axon7toolkit? Use "fastboot flash recovery recovery.img" and you'll be able to avoid using the toolkit. It's finicky as hell.
Otherwise at least use EDL Tool...
Your boot image is untouched. Seemingly axon7toolkit does "fastboot boot recovery.img" which basically sends the recovery to RAM or something and makes the phone boot into that file instead of the actual boot.img.
If you are on Fastboot select "Recovery" from it and hit power. It will enter the recovery directly. This is important because if the phone boots, it will reinstall the stock one.
After you get into TWRP, FLASH MAGISK. This will let you retain TWRP.

Choose an username... said:
Why do you even use axon7toolkit? Use "fastboot flash recovery recovery.img" and you'll be able to avoid using the toolkit. It's finicky as hell.
Otherwise at least use EDL Tool...
Your boot image is untouched. Seemingly axon7toolkit does "fastboot boot recovery.img" which basically sends the recovery to RAM or something and makes the phone boot into that file instead of the actual boot.img.
If you are on Fastboot select "Recovery" from it and hit power. It will enter the recovery directly. This is important because if the phone boots, it will reinstall the stock one.
After you get into TWRP, FLASH MAGISK. This will let you retain TWRP.
Click to expand...
Click to collapse
yeah I don't know why it seemed like a good idea, it's a sticky post in the rom section... It's how I started and then wanted to stick to it somehow.
indeed booting into recovery works like a charm which is already pretty reassuring.
flashed magisk, twrp is not up to date (3.1.1.0), but system boots. thanks a bunch
I guess I'll update / flash the most current version of twrp via fastboot and then go on to flash lineage
again, thank you very much

fleity said:
yeah I don't know why it seemed like a good idea, it's a sticky post in the rom section... It's how I started and then wanted to stick to it somehow.
indeed booting into recovery works like a charm which is already pretty reassuring.
flashed magisk, twrp is not up to date (3.1.1.0), but system boots. thanks a bunch
I guess I'll update / flash the most current version of twrp via fastboot and then go on to flash lineage
again, thank you very much
Click to expand...
Click to collapse
Is your twrp installed as "Keep Read Only" or did you select "Swipe to Allow Modifications"?
After giving flash in the Magisk you gave wipe?
Thanks if you can respond.
Enviado de meu ZTE A2017 usando o Tapatalk

EwertonR19 said:
Is your twrp installed as "Keep Read Only" or did you select "Swipe to Allow Modifications"?
After giving flash in the Magisk you gave wipe?
Thanks if you can respond.
Enviado de meu ZTE A2017 usando o Tapatalk
Click to expand...
Click to collapse
If you're asking because you want to know:
-swipe to allow modifications is okay
-If you want to get rid of encryption, you have to FORMAT data (not wipe). You'll lose the internal storage. After that, flash magisk.
You can just flash it without formatting , but your storage will be encrypted, and you'll lose the internal storage if you ever change ROMs.

I swiped to allow modifications
I backed up everything I needed from the phone. I actually planned for removing everything to get a fresh setup.

Choose an username... said:
If you're asking because you want to know:
-swipe to allow modifications is okay
-If you want to get rid of encryption, you have to FORMAT data (not wipe). You'll lose the internal storage. After that, flash magisk.
You can just flash it without formatting , but your storage will be encrypted, and you'll lose the internal storage if you ever change ROMs.
Click to expand...
Click to collapse
So after installing twrp I format the Data partition and give flash in Magisk, correct?
I am afraid to enter bootloop because I have already done several procedures and in all the same thing happened. I hope everything will work out this time.

EwertonR19 said:
So after installing twrp I format the Data partition and give flash in Magisk, correct?
I am afraid to enter bootloop because I have already done several procedures and in all the same thing happened. I hope everything will work out this time.
Click to expand...
Click to collapse
yes