TWRP boot-loop - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Good evening,
First of all, I want to say I'm a small French who speaks / not understand English,
Then I used Google translator, so my message may confused, you can ask me to rewrite or rephrase the message quoting me with quote ""
The party has a problem with understanding, and I also ask you to avoid maximum, abbreviations or mistakes,
Thank you very much
I currently have a problem with a tablet: Kindle fire HD (Lollipop 5.1.1 Recovery: TWRP)
So now, after many bugs service Gapps I wanted to reset the tablet,
Now the BOOT LOOP tablet, but not a LOOP BOOT-ROM, a BOOT-LOOP TWRP,
Eg: I turn it on, it proceeds as usual:
- First time loading "Kindle Fire" with the word "Fire" in orange
- Second time loading "Kindle Fire" with the word "Fire" in blue
- Now instead of going to the loading CyanogenMod with small blue head, it starts loading TWRP BOOT-LOOP.
"So I do not know how to do, I try to boot into the FAST-BOOT mode using the Volume button down, but without success" --> A little again, I know access the fast-boot mode with adb but I think it takes a modified cable?
(I think I said all possible information!)
Thank you for your help

Finally, I found myself asking why this walk myself I did not really understand, a little anyway, my goal
Was to put the files needed for it to TWRP BOOT normally then make manipulations called "banal" to re flasher
ROM, but made I just changed the attributes of the file 'recovery' and there by magic tablet after some seconds to unlock the BOOT-LOOP on TWRP
and I could finally enter TWRP menu, but again, there was a concern, TWRP tell me that the memory (available / usable) was' 0 mb 'Then I '12 GB' of internal memory
And there it just enough to make a 'Data Format' and my memory was available then usable.
So to exit the LOOP BOOT -> TWRP I used ADB:
Explanation:
- Put the tablet in operation and wait what BOOT LOOP-loading TWRP
- Launched the ADB console, then verified that the ADB connection is made with "adb devices"
- Then explore the tablet with "adb shell"
- Verify that the symbol just left to run a command is '#'
('#' Signify ROOT rights, '$' signify simple user rights)
- Now "ls -l" to see the attributes of files, this command should bring up all folders with their permissions (attribute) W: write / R: read / X: executable.
With any luck, you have the file Recovery, (in my case, these attributes were "d rwx r_x r_x recovery")
- Now we need to change the writing attribute of this file, the command is this: "recovery mattrib w +"
Wait a few seconds and your BOOT-LOOP -> TWRP must stop and you need to access the TWRP menu!
------------------------------------------------------------------------------------------------------------------
Step am perhaps especially to my problem:
follow only if your tablet indicates that your storage space is '0 mb'
- In TWRP menu go to 'WIPE' then 'Format data'
------------------------------------------------------------------------------------------------------------------
- Now get the ADB shell 'with' exit '
- Put your ROM to the folder where you run ADB
- And do the command 'adb push sdcard'
Now you can follow the normal procedure to flash your ROM

Related

How 2 - ADB, Rooting(reflash), Unrooting, Nandroid, Remove/Install App, roms, kernels

So far, this is going to be a guide for noobs. Please read through this, and ask any questions that you have. This has been compiled from different guides around XDA, and information has been stripped that does not relate to our phones. More will be put up here when I find it, and all credit will be provided. This will be from 'duh' to 'didn't know that'. The idea is to provide a beginning to end explanation: Stock Incredible to Rooted with custom Rom.
Topics so far - ADB, Rooting (reflash), Unrooting, Nandroid, Remove/Install Apps, roms, kernels...
I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE DOING ANY OF THIS.... REGARDLESS OF WHY. Yadda, yadda, yadda...
**********At this point, I'm going to ask that you uninstall HTC Sync. Also, please uninstall HTC Driver... (whatever it's called) Nobody likes them (really though, it will mess up a lot of things. You can install them later when all this is done).**********
1) Setting up ADB
ADB stands for Android Development Bridge. It is used by Android developers for programming. For us, it is used to hack into our phones . For our purposes, just know that it is like the cmd (command prompt) that allows us to send commands to our phone. This is extremely useful when we're in the custom recovery
Download the Android SDK from Google: http://developer.android.com/sdk/index.html
Unzip to your desktop
Take the "android-sdk-_**-windows" folder and move it to the root of your hard drive (C:\)
** will change, it is revision of SDK, like "r6"
****The below is not necessary, but is useful sometimes if you just want to run "adb shell" from anywhere without going into the sdk directory****
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-_**-windows\tools
****End of the "This is not necessary thing****
Now, we get USB drivers to work. Some use HTC Sync for drivers, however HTC Sync does not like to play nice with the reflash tool (later on this), so we will use the generic google USB drivers.
1. Run SDK Setup.exe
2. If it gives you any error go to settings and click on "Force http//....."
3. Select usb driver package, let it download and install
4. Some say the below step is not needed, but I did this so I'm posting it
Go to tools folder, and edit "android_winusb.inf" (you can do this by opening it via wordpad). Add the following at the end of the [Google.NTx86] and [Google.NTamd64] blocks:
;HTC Incredible
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94
Save the file and exit.
5). Plug your phone into PC, when windows asks to install drivers for new found hardware, point the New Hardware Found wizaed to android_winusb.inf that you just edited.
============================================================
2) Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
============================================================
3) Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in:
cd C:\**your sdk name**\tools (Press Enter)
adb devices (Enter) You should see your device listed
adb shell (Enter) you should see $ in the next line
**After you obtain root**
su (Enter) you should see # in the next line if you are already rooted
**you may need to allow adb shell to run as root. Look at the phone and see if Superuser.apk is asking for your permission to allow adb root access. Click on "Remeber my selection" and select yes.
Now you are all set to run adb commands as root or as a regular user
**Note: for a list of commands that you can type using adb type "adb" in cmd
All Credit for Topics 1 - 3 go to user XDA member nephron. I mostly copied all of his guide, but updated some information on it to make sense for our phones. Also, removed some stuff I didn't see necessary. Please go to the original thread for the G1: http://forum.xda-developers.com/showthread.php?t=532719&highlight=nandroid+guide for a list of further Credits, and for information I've left out. If you like this thread, please donate to HIM
============================================================
4) Rooting your phone - READ THIS WHOLE SECTION BEFORE GOING TO ANY EXTERNAL LINKS PLEASE. At this point, running the UnrEVOked reflash3 tool will root your phone and install a custom recovery. To try to make it really easy to understand, recovery allows you to access your phone to make PERMANENT changes (something we can't do while booted yet), flash custom roms, and save your sorry little @$$ if you do something that you weren't supposed to
Ok, at this point, I'm going to ASSUME that you don't have HTC SYNC installed (or uninstalled it), and that you have the Google USB drivers installed (i.e. you read at least some of this post). The first thing we're going to do is:
1) Read this: http://forum.xda-developers.com/showpost.php?p=6875912&postcount=1
2) If you read #1, you already went here: http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install
and downloaded the MODIFIED (i.e. changed, not the same, DON'T SKIP THIS STEP) driver and installed it
3) If you read #1, you already downloaded the reflash tool executable
4) If you read #1, you've already done #2, and 3, and this is just a worthless step of me explaining how important it is that you did #1
5) Lets do this. #1,2,3 and 4 were "get ready" steps. By now, you installed the modified driver, went to the webpage and downloaded the UnrEVOked3 reflash tool. HTC sync is also uninstalled. Plug in your phone (normally booted) to your pc and select "Charge Only" when asked how to connect to PC, and click on "remember my selection". Click Done.
6) Unplug Phone from PC.
6a) If you have double twist installed, at this time open the task manager on your pc, and kill doubletwist.devicehelpder....
7) Run the "reflash_package" executable that you just downloaded. Notice the path that it lists and click "install". This will unzip "reflash.exe" and a bunch of other stuff that is needed to the directory that you just noted. Go to this directory (usually the same one where the executable you just ran is) and run "reflash.exe"
8) Plug in your phone.
9) When the program is finished, you should see koush's clockworkmod recovery on your phone's screen and reflash will say that it's done. Congrats, you have root and a new recovery.
If something went wrong, and you're not on koush's recovery and reflash says it's done, don't worry, just re-run reflash. You can run it as many times as necessary. It will not hurt anything AT THIS TIME (this may change later)
10) Koush's recover works a little differently:
a) Vol+ and - scroll up / down
b) the Power button work as a "Back" button, and will turn off screen if you're at the root of the menu. If your screen goes blank, don't read, just hit Power again
c) To make a selection, click the optical trackpad
11) Reboot your phone by highlighting the selection and choosing it
For the most part, these instructions were written from memory, but all credit goes to UnrEVOked, Shadowmite, and anyone that they've given credit to in original links.
============================================================
5) Unrooting - I didn't want to re-invent the wheel, so I'm posting an external link:
http://androidforums.com/all-things...ideo-howto-unroot-incredible-downgrading.html
Just follow the instructions. Credit goes to the OP. If this link ever goes to a 404, pm me and I will find another link with instructions and update this. Also, if you don't understand something, just ask in this thread, someone will answer (maybe even me ).
============================================================
6) Whats is a Nandroid Backup?
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
Nandroid Backup is a tool allowing your Incredible that has koush ClokworkMod Recovery to create a full system backup and restore it, which, when flashing and testing different roms can be very useful.
A) Creating a Backup using Nandroid
Boot up your phone in recovery (Turn off, then turn on while holding Vol- and Power. Press Vol- once to highlight recovery, hit Power once to go into it)
You will now see your new koush recovery
Scroll down (Vol -) to "nandroid" and select it (press the optical button in)
"Backup" will be highlighted. select it
Let it work, it might take a while for a full system backup
Once its done, your backup is complete and is saved on your sdcard in the "clockworkmod" folder. Normally it's stored in the "nandroid" folder, however our Recovery does things a little differently.
B) Recovering to Your Nandroid Backup
Make sure u made a backup and its in the clockworkmod folder on your sdcard
Boot up your phone in recovery (Explained Above)
Go into "nandroid" in the recovery (also explained above)
Select "restore backup" and select from the backups you have (if you have multiple) that you want to restore; this will do a simple, "restore all" of your latest nandroid backup
:OR:
Select "Advanced Restore", choose from the backups that you have on your SD card, and then what you want to restore. You can individually restore "system", "data", "cache", etc....
In "Advanced Restore", i have not seen a way to restore multiple options (cashe AND system, etc...) Koush, am I missing something?
Let it work
Once its done, restore more options through the Advanced Restore menu, or reboot your phone and your selections will now be restored!
============================================================
7) Remove Apps
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
1) Go into Clockworkmod Recovery (With phone turned off, Vol - + Power, then Vol - to select recovery, then hit Power)
2) Select "partitions" from menu, then select "mount sytem" You can also "mount sdcard" if you want to back apps up to sdcard
3) Connect Phone to PC
3a) Open a command prompt and navigate to your sdk\tools directory
3b) Type: adb remount (it shoud return successful)
4) Open Adb Shell on your pc (Type: adb shell)
It should automatically show #, otherwise type "su"
Type:
cd /system/app (enter)
5)Type ls (this will show you all of the stuff in the /system/app directory)
6) To "delete" apps, type the following:
/system/bin/mv Your_APP.apk Your_APP.apk.bak (i.e. CityID.apk CityID.apk.bak). If you want to clear up space on your internal storage for whatever reason, you can replace Your_APP.apk.bak with /sdcard/Your_APP.apk.bak (this will move the app to the root of your SD Card instead of just change it's name)
If you don't get errors, you're done.
*This does not delete apps, but changes their file type so they will not show up as an app, in case you want to get them back at any time later you still have them and don't have to frantically post threads on XDA asking for them.
============================================================
8) Install Apps to /system/app
**Using Koush Recovery:
Power takes you "bacK" in menu's. On root of the menu, it will turn on/off screen. Hit Power again to turn it back on.
Vol+/Vol- lets you scroll up/down through menus
Pushing optical trackpad in makes your selection
1) Place your app you want to install into the root of your sd card (this is easiest)
2) Go into Clockworkmod Recovery (Explained in 7)
3) Mount system and sdcard under partitions (Explained in 7)
4) Connect Phone to PC
4a) adb remount in command prompt (should sow successful) (again, in 7)
5) Open Adb Shell on your PC
6)
IF NOT at #, type "su" to go from $ to #.
Type:
/system/bin/mv /sdcard/Your_App_Name.apk /system/app/Your_App_Name.apk
7) If you don't get errors, you're done. You can unplug phone, and reboot
============================================================
9) Flashing Custom Roms
Download a ROM that you want to try. One of the roms from here are a good starting point: http://inc.sodpit.com/. They are mostly stable might get a few random reboots.
Steps:
1. Download Rom of your choice
1a. Right now, there might be two ROM types, a nandroid backup and an update.zip type file. For right now, I recommend sticking with the update.zip kind. These instructions are meant for it, but I just want you to make sure you know which type it is before you try to flash it.
2. Copy and Paste the downloaded file onto sdcard. Make sure it is not in any directory's of SD card, just on the sdcard (the "root" of it).
3. Verify it's there using Astro or some other File Manager just to be safe.
4. Download and Run Titanium Backup from the Market if you haven't already. (If you don't have it, get it, it's must have for root users.)
a. Select Menu, Batch, Backup user apps. (in Titanium Backup)
b. let it run, this will take some time.
5. When that's done open your command prompt, navigate to your sdk\tools directory, and type "adb reboot recovery" (Not within adb shell, but in command prompt in that directory. I'm not going to explain how to do this because it's already explained above. Also, if you're flashing roms then you're already familiar with it, or maybe you shouldn't be flashing roms ).
6. Do "Wipe data/factory reset" and "wipe cache partition" in Recovery **This WILL WIPE your phone**
7. Select "install zip from sdcard", then select "choose zip from sdcard", then select the name of the zip you want to install.
8. When that's done reboot your phone, once your done setting up all the settings, download titanium backup from the market again, and set that up.
9. In Titanium, Select Menu, Batch, Restore User apps.
After that's done you'll have all your apps that you had before, data included, with a fresh new rom to try out. Hope this helps!!
All credit for these instructions goes to tcbert2010, they were suggested to me, and I liked them. I modified them a BIT, so they make more sense to me and hopefully to you. See post #2 in Original Thread = http://forum.xda-developers.com/showthread.php?p=6953608#post6953608
============================================================
10) Installing custom kernels
I'm only mentioning Hydra's kernels. I'm running the Undervolted, NOT overclocked kernel with wireless N to preserve my battery to get more life out of it
**Taken from website's FAQ**
Q: So how do I install the kernel?
A: First step is to either download the kernel zip file straight to your phone, or download it onto your computer and put it on the sdcard of your phone. Next you turn the phone off hold volume down and power at the same time. When the phone is in HBOOT wait a few seconds for it to initialize then hit volume down once and then power to boot into Clockwork recovery. Once in clockwork recovery you want to select "Install zip from sdcard", then "Choose zip from sdcard". You will now see a listing of files on your sdcard select the kernel zip you downloaded, or if you downloaded strait to your phone go to the Downloads folder and select the kernel zip file. The kernel will now install to the phone and once it's done it will say install complete. Now you can hit the power button once to return to main menu and select "reboot system now" . Your phone will now reboot with the new kernel.
***
Go to: http://hydrakernel.net/ to download the kernels
Please read: http://hydrakernel.net/faq.htm to educate yourself. It's worth it.
Credit to EJHEART for the wonderful kernels! Where are my 2.2 kernels EJ ?
============================================================
Again, if you have suggestions, requests, or whatever please post or PM me.
PM Me if I missed giving someone credit. PLEASE!!!
reserved
reserved for future.
Reserved
reserved for future
Great thread topic... reserved for future use
Updated
Updated with Reflash instructions.
dreamersipaq said:
Help I'm stuck at waiting for system to settle
check these common issues:
- You switched your driver to the one from this post? It's NOT identical to the SDK one.
- You don't have any usb applications that might be taking focus while we are working with the phone right?
- Is the SD card present in the device?
- You did give su permenent access when you allowed it in superuser right?
More to come...
Click to expand...
Click to collapse
Good start, iPaq! I just want to plug Linux AGAIN. I had zero problems using reflash for linux and using Gparted in Ubuntu/Debian/Linux Mint mint means one can do all kinds of things that will become helpful very soon if not already (e.g., manipulate ext and swap partitions on the sdacard!). Aside from linux being Android's native file system, using a Linux distro just makes 110% good sense if you plan to do any developing for the DI/Android. Why poeple struggle so much with Windows when Linux is free is beyond me
2 cents deposited!
Additional items to add
1) After I have rooted and reflashed - How do I flash new ROMs
2) After I have rooted and reflashed - Is there an easier way to get back in and get rid of CityID, etc?
3) How do I update to a later version of ClockworkMod
Great topic
Sent from my ADR6300 using XDA App
...
jdmba said:
1) After I have rooted and reflashed - How do I flash new ROMs
2) After I have rooted and reflashed - Is there an easier way to get back in and get rid of CityID, etc?
3) How do I update to a later version of ClockworkMod
Click to expand...
Click to collapse
1) - Will update soon
2) - I BELIEVE that this works:
1) Go into Clockworkmod Recovery
2) Mount Internal Storage under partitions
3) Connect Phone to PC
4) Open Adb Shell on your pc
Type:
su (will change to #)
cd /system/app
mv CityID.apk CityID.apk.bak
you're done.
Not in front of my phone at this sec, but if mv does not work, try
busybox mv CityID.apk CityID.apk.bak or
/system/bin/mv CityID.apk CityID.apk.bak
*This does not delete it, but changes the file type so it will not show up as an add, in case you want to get it back at any time later.
If I'm wrong please correct me.
3) The easiest way to update recovery at this time is through Koush's Rom Manager. However, at this time I've read somewhere that it's not persistent. Let's give this a few days.
Updated
First Post Updated.
here is my problem, apparently when I got root I didn't push superuser.apk as a system app correctly.
SO, I have root in the OS after each boot, once I install superuser.apk.
Problem is, I can't get back in recovery to fix this. I have gotten into recovery with ADB again (maybe twice in the 2000 times I have tried again), but when I get to the step where you do the update and push the zip file at the same time, it never works now. So I am unable to push the apk as a system file.
So, the unrevoked recovery flash fails because it doesn't have su rights when it gets to the os on reboot.
Anyone want to help me out?
qwho said:
here is my problem, apparently when I got root I didn't push superuser.apk as a system app correctly.
SO, I have root in the OS after each boot, once I install superuser.apk.
Problem is, I can't get back in recovery to fix this. I have gotten into recovery with ADB again (maybe twice in the 2000 times I have tried again), but when I get to the step where you do the update and push the zip file at the same time, it never works now. So I am unable to push the apk as a system file.
So, the unrevoked recovery flash fails because it doesn't have su rights when it gets to the os on reboot.
Anyone want to help me out?
Click to expand...
Click to collapse
Take this opportunity to flash up to HBOOT 79, wipe, and re-root. Start fresh. Re-reflash w/unrevoked2. Alles in Ordnung! At least, that solved all of my problems. Start with the big headache to avoid later headaches. Once you have a nandroid of a "proper" root, you'll never have to do the annoying initial root again.
So you can get HBOOT 79 how? by flashing the latest HTC rom RUU?
qwho said:
So you can get HBOOT 79 how? by flashing the latest HTC rom RUU?
Click to expand...
Click to collapse
Exactly. Doing will wipe out all userdata, everything not stored online, on your card, or on internal disk. It's really the best way to go, to start fresh and remove all the little variable piecemeal rooting has placed in your path to date.
can you point me to the RUU you would use? I did some searching, here and at htc.com, and I couldn't find an RUU anywhere.
qwho said:
can you point me to the RUU you would use? I did some searching, here and at htc.com, and I couldn't find an RUU anywhere.
Click to expand...
Click to collapse
Just down this, run it in Windoze, and before it tries to flash (you don't need your DI connected!), go into your AppData/temp directory, find the ~142mb rom.zip file, rename it to PB31IMG.zip, put it on /sdcard root directory, boot into bootloader, let the card/file get picked up while holding down-volume, ok the flash, no need to ok the reboot, then boot into to recovery and proceed with adb shell/rooting process one
I've been having some trouble with the nandroid step, and creating a backup. I've done everything listed prior to that with success, but when I load into recovery I don't see the option to create a nandroid backup. I have also dl'ed RomManager and have tried to create backups through that.
I also dl'ed the unrevoked reflash and tried running that, but that also fails. I'm not really sure what I'm doing wrong, so any help wold be appreciated!
sanchagrins said:
I've been having some trouble with the nandroid step, and creating a backup. I've done everything listed prior to that with success, but when I load into recovery I don't see the option to create a nandroid backup. I have also dl'ed RomManager and have tried to create backups through that.
I also dl'ed the unrevoked reflash and tried running that, but that also fails. I'm not really sure what I'm doing wrong, so any help wold be appreciated!
Click to expand...
Click to collapse
Not sure what you mean. Go into Hboot, and select recovery. When Koush's recovery loads, use Vol- to highlight "nandroid". Click the optical button in, and you'll enter another menu. Select the first option, which should be highlighted by default, which should be "Create Backup" or "Backup Device" or something like that.
Let me know if that works.
When I go into recovery the only options I get are:
Reboot System now
Apply sdcard: update.zip
Wipe data/factory reset
Wipe Cache partition
----------------------------------
E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
I'm not seeing anything about nandroid backup. I'm assuming I'm either not doing something correctly (I'm currently not booting into recovery while running reflash.exe) or somehow the clockworkmod isn't correctly installed.
Any ideas? Or what other information could I give you to help better answer my question?
sanchagrins said:
When I go into recovery the only options I get are:
I'm not seeing anything about nandroid backup. I'm assuming I'm either not doing something correctly (I'm currently not booting into recovery while running reflash.exe) or somehow the clockworkmod isn't correctly installed.
Any ideas? Or what other information could I give you to help better answer my question?
Click to expand...
Click to collapse
You can't install anything to recovery that will stick until you get root via procedure 1, then reflash with unrevoked 2. Sounds to me like you've gotten ahead of yourself

Asus MeMO Pad 7 unusable please help!

Hi,
I am really desperate! I turned on my rooted Asus MeMO Pad 7 ME176CX after several months of no use, but apps/services won't load (loads of error messages, all apps/services stopped etc.) like it was obsolete or screwed up. So I unrooted it and the issue got worse!
There is a Asus demo app in the notification bar that disables WIFI and software reset and says to plug in the power adapter (no difference, it won't go away).
1) I copied the necessary files to my memory card (to get rid of the Asus demo app as per other threads) but once I insert the memory card, even though it is recognized, it says no files present.
2) I did a hard reset with Vol - (or +, tried both) and Power but nothing happens (no recovery screen, it just stays black).
3) I removed the battery & waited 10 mins, no difference.
4) I formatted a card to FAT32 and copied the cleardata.zip unzipped files from Asus then rebooted pressing just Power but it just reboots normally like the card is not inserted.
Now basically the tablet shows a few apps (Calendar, Gallery etc.) and nothing else.
I cannot connect to wifi, bluetooth does not work, the memory card says no files present, vol + power does not work, cleardata trick did not work, I cannot send it back under warranty (ex-rooted) ... what else can I do??????
Many thanks!
Reboot into Droidboot (Volume Down + Power IIRC, could be up), boot the Temporary TWRP (http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096), flash ROM
After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????
boredfish said:
After a few experiments gone wrong I have now bricked the tablet for good (erased all data).
I can ONLY go from the dead droid to 'Android system recovery' which shows:
- reboot
- apply update from ADB
- wipe data
- wide cache
After 'wiping' the only option available is 'Apply update from ADB', so I installed ADB on my Mac and downloaded a few ROMs from the Asus site (even though their page says ME176C not ME176CX, but there is no ME176CX page there).
If I run adb devices from the terminal I see nothing. Only if I select 'Apply update from ADB' on the tablet I see the device from terminal, I believe it opens a bridge to the computer only with this option running. The command 'fastboot devices' never shows anything regardless.
I run 'adb sideload update.zip' (tried with several ROMS) but it always fails AFTER the transfer (either with messages 'status 0' or 'end of footer not 0xFFFF' etc.).
So now I am stuck with adb sideload never working, is there anything else I can do????
Click to expand...
Click to collapse
Well, theres quite a lot of options do recover your tablet, before doing anyhing, if you have access to adb, then you should do: download .17 rom and extract it, after extracting go to META-INF\com\google\android\updater-script and open it with notepad, and remove the first 2 lines, then save, and make the zip file (rename it to update.zip {careful not to make the file "update.zip.zip"}), then put the zip file in adb folder (for me its C:\\adb) and do adb push update.zip /sdcard/ (make sure adb is working) after it finishes pushing, go to bootloader (if not there already) and run temp recovery (twrp or cwm), and then install the zip, then clear dalvik and cache, and reboot, if first reboot doesnt work, reboot again, if it still doesnt work, install update.zip again. Hope i helped, if u have any questions tell me :3
=====
edit
=====
if you really cant get out of recovery theres still a way of fixing your tablet (same problem happend to me today and its fixed), if you already did all the steps above on the download .17 and extracting and changing the file of updater script then its already almost done, to access the bootloader you need to shutdown your tablet, press Power, Vol+ and Vol- at same time, it will go to fastboot, copy the file "droidboot.img" from the update.zip and place it in the adb folder (for me its c:\\adb), then do "fastboot boot droidboot.img" and it should download the img to the tab and boot to droidboot (you need to do this a few times, because 5/1 only 1 goes to bootloader), after booting to droidboot you can easily recover from there, on bootloader you have adb access, which means you can push the update.zip to the tablet (with update.zip in adb folder already, do on cmd, "adb push update.zip /sdcard/") after pushing go to temp recovery and install the update.zip normally after installing. format cache and dalvik, and reboot, if its stuck on logo, shutdown and reboot, if still doesnt work install the update once more by turning your device off and go to bootloader normally, (it works now, because it has the software now, (to enter bootloader press press power + vol-), and load temp recovery and reinstall). i hope i helped

Fixing 'Cannot Mount /data' when everything is deleted, Internal Storage = 0mb

Alright, I got out of that issue, now its time to tell you how I did this.
Key:
- equals Start of Section
= Equals End of Section
-------------------------------------------- Fixing ADB Recognition (Optional But Vital) ------------------------------------------
First of all, follow my other thread on fixing bootloader being recognized as an android bootloader interface or do this
1. Do steps in this thread up to step 5,1
2. Delete the drivers for the child of Android Device by right clicking the device and press Uninstall Driver, then check the box Delete Driver for this Device. Don't worry, the drivers you installed will not go, it will just delete the watch from being recognized
3. Disconnect your watch then reconnect it
4. You're computer will not recognize this device and it will be placed under the category, in the device manager, as 'other Devices'
5.---- 'Copied from my other thread and changed'------
5,1. Right click on the children of the unknown device
5,2. Go to Drivers and press Update Driver
5,3. Press Browse my computer for driver
5,4. You will be prompted a directory, instead press the button below it called 'Let me pick from a list of Drivers installed on my computer'
6. Locate to ADB Devices or Similar
7. Select any one of the drivers listed inside there
8. Done.
=============================================================================================================
----------------------------------------------------- Installing System and Boot and Recovery (VERY IMPORTANT) -----------------------------------------------
This is where, if you do not change your TWRP to factory recovery, your watch will re boot into TWRP because it cannot mount /data. By flashing the factory Recovery, you will eliminate this and you will have a fresh start into the system.
Prerequisites ( If you Do not have it, which you should):
simple adb here
1. Get the system, boot and recovery from this thread by IntersectRaven
http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964
2. Once you have downloaded those, assuming you have done the optional procedure before this, boot/stay into fastboot
3. Place the files into the location where the simple adb is located
{{{ THIS IS THE PROCEDURE YOU SHOULD FOLLOW IN THE FOLLOWING STEPS BECAUSE THAT IS HOW I DID IT }}}
4. first check your device is seen in fastboot by typing
Code:
fastboot devices
5. once your device is seen, active and has a tag fastboot. follow on.
6. Flash the stock system first by using this code
Code:
fastboot flash system yoursystemfilename.img
replacing 'yoursystemfilename' only with the name inside the simple adb
7. Flash your boot by using this code
Code:
[CODE]fastboot flash boot boot.img
[/CODE] where 'boot' is a defined variable in your simple adb folder
8. lastly, flash the STOCK recovery by using this code
Code:
fastboot flash recovery recovery.img
where 'recovery' is a respectable variable in your simple adb folder
9. disconnect and start your system!
=====================================================================================================================
References (for the past 4 weeks):
Emergency Guide
Stock boot,sys and rec
Click to expand...
Click to collapse
Please like and upvote if it helped, as I had to take time off my studies to do this.
Also tell me if there were any mistakes.

How To Guide How to install Omnirom - the complete guide

Install OmniRom 12 / 13 on Asus Zenfone 8​FOLLOWING THIS GUIDE WILL VOID YOUR PHONES WARRANTY, ERASE ALL YOUR DATA ON THE PHONE AND IN SOME RARE CASES POSSIBLY BRICK YOUR PHONE.
THE AUTHOR OF THIS GUIDE IS NOT RESPONSIBLE FOR ANY CONSEQUENCES IF YOU USE THIS GUIDE. YOU DECIDED TO DO THIS AND YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Prerequisites:​Downloads:
- vendor_boot.img
- LOS_recovery.img => Recovery image
- Omnirom.zip
Place them all in the same folder on your computer
Install and setup ADB and Fastboot
How to install Omnirom​
BACK UP ALL YOUR DATA ON THE PHONE, THEY WILL BE DELETED IN THE PROCESS!!!!!!!!!!!!!!!!!!
Update your phone to the same android version as the rom you want to install. And yes you have to install all updates until you reach the desired android version.
Install the Asus-Unlock-App from the asus website
Use the unlock app to unlock the device. Reboot. Your device will perform a factory reset,
Set up the phone, skip what you can and enable the developer options:
Settings => System => About Phone => Software-Version => Tap on Build-Nr. until the message "You are now a developer" appears.
Go to the developer options: Settings => System => Developer Options and enable "USB-Debugging".
Install ADB and Fastboot, for Windows install additionally the drivers from the asus website.
Plug your phone to your computer with the original cable. Accept USB-Debugging and allow it permanently.
Open a terminal/command window and navigate to the directory where your rom and LOS_recovery are stored. Type:
adb devices
It should show something like "ALOTOFCRYPTICSTUFF device", if that is the case type:
adb reboot bootloader
Once the phone is in Bootloader mode type:
fastboot devices
It should show something like "ALOTOFCRYPTICSTUFF fastboot", if your device shows up, type:
fastboot flash vendor_boot vendor_boot.img
Wait until it is finished and then:
fastboot flash boot LOS_recovery.img
Wait until it is finished and then:
fastboot reboot recovery
Factory reset => Format data
Select apply update => ADB Sideload
On your computer (still in the directory with all the files) type the following:
adb devices
It should show something like "ALOTOFCRYPTICSTUFF sideload", if that is the case type:
adb sideload name-of-your-omnirom-image.zip
Wait until its finished, check the screen on the phone. If it says "Signature verification failed" on the phonde display just click yes.
On your computer it may get stuck at 47%, but it keeps on going, be patient and wait until it shows on the phone display that sideloading is finished.
When its finished you can go back to main screen and reboot your phone. Be patient, it will reboot once or twice and take some time. If it didn't boot your rom within a few minutes something in wrong.
If all went well, you will be presented with the start screen of your newly flashed rom.
If all goes perscheid: How to recover your phone:​Prerequisites:​You have to decide if you want go back to or restore Android 12, then take the image from download A, if you want to stay on or upgrade to Android 13 then download B.
Download:
A. A13 to A12 raw image from the asus site
B. A13 Beta raw image
Recover your device​
Unpack the downloaded zip files and navigate your terminal/command window into the unpacked folder
If your phone bootloops or is stuck at the asus logo:
Press Volume down and power button until the screen gets black and then immediatly press volume up and power button until the you see the bootloader screen then release the buttons
Check if ADB can see the device by typing:
adb devices
It should show something like "ALOTOFCRYPTICSTUFF device", if that is the case go to the next step
In the folder from step 1:
On linux: sudo sh update_image.sh
On windows: commands-to-use-a-batch-file update_image.bat
and wait until the the script is finished and you have to press any key (only enter works)
Boot the stock rom, set up your phone and start again but you can skip step 2 & 3 (unlock the bootloader). Don't forget to enable USB-Debugging before you start to do anything.

[GUIDE] Installing Lineage 18.1 (& more) [X00H] [X00I]

In this guide, i'm going to be a bit straightforward on how to install LOS 18.1 on your X00H/X00I device.
For the process, you need:
Your X00H/X00I device;
The following must be unlocked (if you didn't, you can follow the howto over my post);
A rooted phone/tablet with Magisk (any ADB & Fastboot tool is fine, but i suggest using this for simplicity);
In case you have none of the above, even a PC or Laptop with ADB and Fastboot binaries installed will suffice;
If you're on Windows, you can get the installer over GitHub;
If you're on Linux, hop into your package manager and install them via terminal (the following example will be for Debian/Deb-based/Ubuntu/Ubuntu-based distros. If you're on Arch, Fedora, etc.: just search for "fastboot" by using the respective pkg manager's search flag, then install it basing from the name it's repo gives):
Code:
sudo apt install fastboot
An USB cable (should come into the device's box, also must be capable of data transfering);
If you're going to do the process via a rooted device, the Asus device should come in it's packaging with an OTG adapter (be sure to attach the following to the rooted device);
PBRP (Pitch Black Recovery Project) for the device- OG post can be checked here;
Latest version for X00H;
Latest version for X00I;
If your device is an X00I, you can alternatively get TWRP instead;
The Android 9 Beta update (you MUST have the device updated to that version, else you'll risk the device to be bricked- for more info, check the OG post by Seba);
If you want to flash it via stock recovery, you can get the file over ASUS' site on the device;
Download for the X00H;
Download for the X00I;
If you have already flashed a custom recovery on your device, you can get the "custom recovery flashable zip"over SebaUbuntu's site;
.zip file for the X00H;
.zip file for the X00I;
Tiny discalimer on the flashable .zip above: once installed, your device's recovery will be replaced to stock (in other words, you'll lose the custom recovery);
The Lineage OS 18.1 rom and recovery (credits to @miya0405 for finding the site);
ROM and LOS Recovery for the X00H;
ROM and LOS Recovery for the X00I;
If you have all of the things required in the list, let's go!
--------------------------------------------------------------
Installing the Android 9 Beta​Stock Recovery method:​
Download the Android 9 Beta over ASUS' site (any device is fine, even using the phone itself);
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery (do Power + Vol.up combo- if your device's unlocked, tap on the volume button and select "Recovery" by pressing on the power button to confirm);
Select "Update from sd card";
Select the .zip file you've downloaded;
Wait for the update to install;
After updated, go back and select "Power off";
Custom Recovery Method:​
Download the Android 9 Beta flashable .zip over SebaUbuntu's site;
Put an SDCard inside the device;
Move the .zip file inside the SDCard;
Turn off the device;
Boot into recovery;
Select "Install";
Select the "External Memory" storage;
Search for the .zip file inside the SDCard;
Tap on it and install it, unchecking everything;
Swipe to continue and let the .zip file install;
The recovery will print you text on the progress (also gives advice on what to do after install);
Reboot to system;
Power off the device;
----------------------------------------------------------------
Unlocking the device:​Just a tiny reminder if you haven't yet, check my guide about it: then, resume from this point and proceed;
----------------------------------------------------------------
!!A word of advice!!​Don't install PBRP recovery just yet!
If you'll pick PBRP instead of the LOS recovery as the custom recovery of choice, flashing LOS 18.4 with it should make Lineage 100% unbootable and stuck in a bootloop!
Don't reboot back to PBRP if bootloops happen:
neither don't fix the "Cache" partiton with it, else it'll cripple more Lineage and redirect the boot to recovery or fastboot/bootloader!
TL;DR: Don't do my same mistake and flash the recovery partition with the wrong recovery (on the bright side, the device will still be salvageable).
----------------------------------------------------------------
Flashing Lineage Recovery:​Before proceeding, do the following firsthand:
Be sure to have the ADB & Fastboot binaries installed;
Your device rebooted to fastboot/bootloader mode (any method is acceptable);
Must have downloaded the recovery for your specific model (links are on the "required" list);
The device must be connected to the host machine (if you're using a rooted phone, be sure to have the OTG adapter connected to it first);
Rooted Android Device Method:​
Open the "ADB & Fastboot"tools of your choice;
Whether it is a terminal or the app i've suggested earlier: this portion will purely give instructions if you have the app;
If you're going to do the process via terminal, then jump to the "Linux Method" instead;
If it is the first time you open the tool, it should ask for root perms.- allow them;
Tap on the top right corner of the UI;
Tap on "Fastboot";
Tap on "Refresh";
Go to the "Partition" title, next to it you should see a dropdown menu;
Select "recovery";
Tap on the "Flash" button;
A file manager should open: search where the lineage recovery is (typically you can find it in the "Download" folder. The file should be called "recovery.img");
After selected, the app will automatically flash the recovery for you;
Disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Linux Method:​
Open the terminal (use the shortcut CTRL+ALT+T to open it, preferrably);
Do the following:
Code:
lsusb
# This checks if your asus device is connected proper to the machine
# If it is, lsusb should output something around a "Google" or "Qualcomm" device on the ID Bus
cd Downloads
# If you have put a different language locale, cd into the Downloads folder with it's localized name
ls
# List for the files inside the folder. You should see a file called 'recovery.img' inside
fastboot devices
# Tell fastboot to check if any device on bootloader/fastboot mode is connected
fastboot flash recovery recovery.img
# Gives fastboot the instruction to flash the .img file to the desired device's partition, which is the recovery in this case
After done flashing, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
Windows Method:​GUI Method:​
Simply use the "Latest ADB Launcher"executable located on the desktop of your PC;
Just make sure to flash the recovery partition with the "recovery.img" file;
Terminal Method:​
Navigate with the File Explorer;
Go to your Downloads folder and find for a file called "recovery.img";
Cut and paste it to where the ADB and Fastboot tools are installed at;
Click on your mouse's right button;
Select "Open terminal here" over the contextual menu;
A terminal should pop-up (Command Prompt, that is);
Type in the following:
Code:
fastboot devices
fastboot flash recovery recovery.img
Wait for the recovery to flash on the device;
After done so, disconnect the device;
Navigate over your Asus device with the volume buttons;
Select "Reboot recovery" and confirm with the power button;
Hooray, you have LOS Recovery installed;
------------------------------------------------------------
Installing Lineage OS 18.1:​Before proceeding, do the following firsthand:
Your device must be turned off;
Must have deleted the Android 9 Beta .zip file from the SDCard, for avoiding accidents;
Download the Lineage file off of the "required" list's links for your specific model;
Put the downloaded .zip file on an SDCard;
Insert the SDCard inside the device's slot;
Boot up into recovery mode;
Select with the volume keys "Apply Update" > "Apply from sdcard" and confirm with the power button;
Select the LineageOS .zip file;
Confirm with the power button;
Let the rom install by the recovery;
After install, navigate to the back button with the volume keys;
Select "Factory reset" > "Format cache partition";
The recovery will ask you the following:
Code:
Format Cache?
THIS CAN'T BE UNDONE!
Select "Yes";
Go back;
Select "Reboot system now";
First bootup will take some while, but you'll be greeted by the setup screen in no time.
Congratz, now your device has Lineage OS installed!
-------------------------------------------------------------------
Extras/FAQ Section:​Q: Is it possible to get root priviledges on the device?​A: Sure! There are different ways to apply root on the ROM, but feel free to pick whichever method you like:​
Rooting your device by picking it's 'boot.img' (exactly located on the folder of the respective model) over SebaUbuntu's Lineage site and patch it with an already-rooted device that has the Magisk companion app installed (requires no recovery patching, but it is required to boot the asus device in fastboot mode and patch the boot partition);​
Downloading the Magisk companion app over it's GitHub page, rename the .apk file by replacing '.apk' to '.zip' via file manager, patch PBRP over the recovery partition (with one of the methods listed over 2 titles above this one), and install the 'magisk.zip' file like you could usually do on any other device with custom recovery;​
If you use an X00I device, you can preferrably install TWRP from here instead of PBRP;​
After applied root on the device, patch back on the device the Lineage recovery- just for avoiding any inconvenience if you want to factory reset the device;​
Q: My device has Lineage installed, but the bottom buttons don't work. Is there a way to enable a virtual navbar?​A: Yep, but it's a bit of a tricky process. You must have either apps like Terminal Emulator or Termux installed for making this work- as an extra, you could get other keyboards like BeHe Keyboard or Hacker's Keyboard: but that is only if you've picked Terminal Emulator as your choice.​For direct instructions, follow this (you must be inside the terminal app of your choice and already gave storage perms to it firsthand):​
Code:
su
mount -o rw,remount /
vi /system/build.prop
# After come this far, go to the bottom of the build.prop file by scrolling with the touch screen
# On your keyboard, press the I key. This should make vi enter into INSERT mode
# When done so, add the following line on the build.prop file
qemu.hw.mainkeys=0
# For getting out of INSERT mode, find on your keyboard or terminal UI the ESC button
# For quitting and saving the file on vi, type the following
:wq!
# This should make vi quit and save the modifications to the build.prop file
# For rebooting the device straight from the terminal, just type in
reboot
# The device should immediately reboot, and upon unlocking: the virtual navbar should appear
Q: Can it be possible installing MicroG on the device?​A: You can! Every method for installing MicroG perfectly works on this ROM;​
Q: I have MicroG installed on my device, but i want to apply signature spoofing for extra functionality. Is this possible?​A: Sadly, due to the tinkering i've done on my side: the ROM gets a meltdown when modifying the 'services.jar' file is involved (root or non-root). If you follow some guides online (despite being few), the ROM, regardless of what you do or which method you follow: ​it will end up in a bootloop (or, to be more specific, the SystemUI starts to become picky);​
------------------------------------------------------------------
Credits:
miya0405 (for the lineage site)
SebaUbuntu (for the LOS rom, recovery, and PBRP recovery)
Erwin Abs (PBRP Recovery)
aaaaaaziskurnia (TWRP recovery for the X00I)
You, for dedicating your time on reading this long guide!

Categories

Resources