Database Users

bricked kindle - unlike any other

Situation is this, replaced build.prop file with one from here...it bricked me I believe...
anyways, i get to boot past the logo, then a black screen
adb sees my device, but it doesnt seem to be rooted anymore
cant run adb root or push any files it seems
anyone think of a way to get around this and fix?
thanks

You don't have TWRP installed to mange/install/backup ROMS?

no I do not, I'm an idiot.

Same thing has happened to me. And others I have read on the site too.
No one seems to be able to do anything about it. I tried this http://forum.xda-developers.com/showthread.php?p=20852507.
But all it did was break the adb ability, and instead of a black screen after the splash screen, it changed to just having the splash screen on constantly.
Does anyone have any advice?
---------- Post added at 10:35 AM ---------- Previous post was at 09:59 AM ----------
okay okay. I got somewhere.
Do this: http://forum.xda-developers.com/showpost.php?p=20755810&postcount=1
Then once you have it stuck on splash screen do this:http://rootzwiki.com/topic/12363-ho...our-kindle-fire/page__pid__301703#entry301703
Although ignore the ADB part because I couldn't fastboot with adb and once I did the fbmode thing I couldn't adb but I could fastboot. I am stuck on the yellow triangle at the minute but hopefully I can go from here.
---------- Post added at 10:44 AM ---------- Previous post was at 10:35 AM ----------
taseedorf said:
Situation is this, replaced build.prop file with one from here...it bricked me I believe...
anyways, i get to boot past the logo, then a black screen
adb sees my device, but it doesnt seem to be rooted anymore
cant run adb root or push any files it seems
anyone think of a way to get around this and fix?
thanks
Click to expand...
Click to collapse
Don't give up. There is away around this and it is simple enough.
Read my above posts and try and get somewhere.
I literally just figured it out for myself and we had the exact same problem.
If you need help I just ask. I will keep checking back to see how you get on

Download the fbmode binary and TWRP installation image (twrp-blaze-2.0.0RC0.img).
Extract the stock build.prop from the Amazon update binary (update-kindle-6.2.1_D01E_XXXXXX.bin). Then run the following...
Code:
adb push fbmode /data/local/tmp/
adb shell /data/local/tmp/fbmode
adb reboot
You will then be stuck at the Kindle boot screen. Don't worry though, you are currently in fastboot mode. Now do the following...
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
Your device will reboot to install TWRP recovery. After installation is completed, tap on "Reboot". Once it reboots, you will need to boot into TWRP recovery.
From there, you go to "Mount" and mount the system partition. Then run the following...
Code:
adb push build.prop /system/build.prop
adb shell chown 0.0 /system/build.prop
adb shell chmod 644 /system/build.prop
Now just reboot and you should be set.
If you don't want TWRP and FireFireFire installed, you can install the Amazon update binary via TWRP.

i was figuring the fix was something like that...if it works, ill post my process....please post your donate link so if it does i can buy you some beers

I love you
Thank you so much. Worked like a charm. All I needed to do was chmod 777 to the tmp directory (don't know why...) Problem before, was I was trying to push that to my kindle without it being in fast boot mode, so it always said waiting for device... it was late, so I wonder what I was putting it into...
ANYWAYS, thank you.... and there is another person with this problem I discovered..so you will have helped them too. THANKS!

Nexus 7 Stuck on Google Logo

Good day everyone,
My friend was updating her Nexus 7 and suddenly the connection went off and the update was stopped. When she booted her Nexus 7, it is stuck on the Google Logo and stays there.
If I press the Volume Down, I can get the Recovery, Bootloader or Shutdown. I tried the Recovery mode but still stuck there.
What to do? Is there anyone that can give me the right steps to get back the Nexus 7?
Thank you a lot.

Flash the stock boot.img using ADB
type “fastboot reboot-bootloader”
type “fastboot flash bootloader bootloader-grouper-3.34.img”
type “fastboot reboot-bootloader”
type “fastboot flash boot boot.img”
Hope this helps

sorry for my ignorance but how to flash the stock boot.img using ADB ?
Sorry again and thank you for your help

Aleksee said:
sorry for my ignorance but how to flash the stock boot.img using ADB ?
Sorry again and thank you for your help
Click to expand...
Click to collapse
Like I just told you, their the actual commands mate.
Open CMD by using Run -> CMD -> (NAVIGATE TO YOUR FOLDER)
E.g. cd c://mydocuments/adb/
Im guessing you have ADB installed, as you've already rooted and flashed.
When in the ADB directory, use
adb devices
With your tablet plugged in and USB Debugging enabled!!!
If this lists your device, then you're all good to go with flashing the boot.img
Hope this helps.
If you get stuck, google Flashing Boot.img with ADB on Android
Or something
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
Or use the GUIDE that is on the first page, just above your post.
http://forum.xda-developers.com/showthread.php?t=1907796
^.-

How to unroot the latest RUU (5.07) [GUIDE]

Here is a quick guide on how to unroot the latest RUU 5.07. It seems that quite a few people are having trouble unrooting their device or running an official RUU while being on the latest update, or a ROM based on the latest update.
The problem is that HTC has fixed the bootloader (in particular Hboot 2.18) so that it will reject any PC36IMG.zip official software or RUU files that update previous operating systems on the phone (a S-ON phone). You would usually need a RUU (I'm calling both the PC3IMG.zip file and the RUU file an RUU) that is for your current operating system. If your phone is on the latest 5.07 update or a ROM that is based on the 5.07 update, then latest RUU that exist is for the Evo with RUU Supersonic 4.67. 5.07 never came out, done intentionally by HTC I believe. So none of the RUUs which exist today will work with the 5.07 update. The problem exist because the phone's misc partition is updated whenever you accept an update or run a RUU from HTC, or even flash a ROM. There are other cases as well. The only way to run an official RUU on a phone that is not currently S-OFF is either to downgrade the phone's misc partition, or to turn the phone S-OFF (which you will still have to flash the phone's misc partition to do).
What I've done is put together a quick guide for those who need (or just insist) on unrooting their Evo. It is brief and only for a PC (not a Mac). Hopefully, someone in the future can provide further details or make it Mac friendly or even more user friendly because I don't have a Mac, nor the time to spend to make this guide perfect. I have another phone too to deal with. Remember too, that everything is done at your own risk. So if something goes wrong, well you knew the risks.
For this guide I'm going to assume that you are on Hboot 2.18, the phone is S-ON, the bootloader is unlocked (UNLOCKED), and that the phone's ROM is currently rooted. If not, then this is not the right guide for you.
1. Download this zip file. It contains the necessary files that you will need.
https://dl.dropbox.com/u/38127313/sdk.zip
2. Plug your phone into your computer. Then go to Settings/Applications and uncheck Fastboot. Then goto Development and make sure that USB debugging is now checked. If you have a custom ROM, then the locations of these settings may be slightly different.
If you need the HTC drivers, then I have also included the drivers.exe file that you must run from your computer to install the "MyHtc" drivers that you must have under the computer's device manager when the phone is plug in.
3. Next, unzip the file to a folder, preferably sdk. Rename the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed" file to PC36IMG.zip (not PC36IMG.zip.zip). Place the phone into "Disk drive, then copy the PC36IMG.zip file to your sdcard. Afterwards, don't forget to change the phone back to "Charge only".
4. Next you will need to open a command prompt at the folder where you extracted the files. If you are not familiar or uncomfortable with adb commands, then I cannot help you here.
5. Type or copy the below commands exactly as they appear.
adb push flash_image /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb push mtd-eng.img /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb shell <ENTER>
(You should see either a dollar sign ($) or a pound sign (#) at your prompt, depending on your ROM. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
su <ENTER>
(You might not need this command depending on your ROM, and also you should check to see if your phone is asking for superuser permissions. If everything went Ok, you should now see a pound (#) sign at your prompt. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
cd /data/local <ENTER>
(You need to be in the directory where you put the flash_image and mtd-eng.img files).
chmod 755 flash_image <ENTER>
(flash_image needs to be assigned permissions).
./flash_image misc mtd-eng.img <ENTER>
(This is the most critical step here).
reboot bootloader <ENTER>
(I prefer this step, as it is much faster than pulling the battery and all that other stuff that people suggest).
The phone should now reboot directly into the bootloader. Also the phone will now be locked again (LOCKED OWW) regardless of its previous state. Next hit the power button. It will then take some time to read the PC36IMG.zip file. If everything went Ok, then it should ask you whether or not you want to accept the update, which means that your misc partition was successfully downgraded, and now you can successfully run the RUU.
EDIT: I have to re-upload the sdk.zip file, because the original one had a problem with the PC36IMG.zip file. It should be available shortly. The one I added does work this time; however, the phone may have to be updated in order to bring it back to the latest bootloader and update. It's not the latest RUU 4.67, but the second latest 4.54. I cannot believe that something was wrong with that file. Also, instead of the PC36IMG.zip file that I added, you could also use any other PC36IMG.zip file or a RUU.exe file from HTC. They should work as well. I would not recommend a RUU below Supersonic 3.70. I'm going to upload some of these as well when I get a chance. I have like all of them.

Re: How to unroot the latest RUU (5.07)
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium

CNexus said:
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Thanks for the advice. I'm currently re-uploading the sdk.zip file. Something went wrong with the PC36IMG file. It should be available again in a little while.

I wonder if you can help me?
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
---------- Post added at 09:12 PM ---------- Previous post was at 09:05 PM ----------
6foot5nbad said:
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
Click to expand...
Click to collapse
BTW, Bootloader is still unlocked

If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery /path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100

CNexus said:
If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery / path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100
Click to expand...
Click to collapse
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.

update
6foot5nbad said:
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.
Click to expand...
Click to collapse
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------
6foot5nbad said:
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
Click to expand...
Click to collapse
Also, I would need help on how to push the recovery log file to /data/data/recovery/log if possible or would it simply be adb push log /data/data/recovery/ ?

An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100

CNexus said:
An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100
Click to expand...
Click to collapse
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
---------- Post added at 12:24 PM ---------- Previous post was at 11:59 AM ----------
6foot5nbad said:
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
Click to expand...
Click to collapse
I forgot to mention, the TacoRoot Exploit requires the recovery log file (http://rootzwiki.com/topic/13713-tacoroot-htc-universal-root-exploit-12-30-2011/) to be in /data/data/recovery/ directory, so it requires a user to boot into recovery to create the log file, and I can't boot into recovery.... so my idea is to push the recovery log file to /data/data/recovery/log cause thats where the exploit is looking for the log file. I'm hoping that will prevent me from having to boot into recovery which is where I'm getting stuck on the tacoroot exploit. With shortydoggs guide, I'm getting stuck at the "su" command cause the evo (for some reason) isn't rooted anymore. So my plan is to get me temp root with TacoRoot so I can get "#" and continue with shortydoggs guide. Not sure if that's possible but at this point its my only option since I can't get into recovery to flash su.zip nor can I RUU cause I'm on 5.0.7 which has no RUU.

I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.

Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Sent from my PG06100

Thanks!!!
shortydoggg said:
I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.
Click to expand...
Click to collapse
Thank you and CNexus. I'll try it and let you know how it went. I probably will fool around with it tomorrow sometime so I'll get back to you then. Going back a little, after I pushed flash_image and mtd-eng.img to data/local/, I noticed a blue status bar while in hboot, I'm assumming its searching for the pg36img.img update...... that said, is it necessary to push those files again?? BTW, great guide and write up. Thanks for everything. http://forum.xda-developers.com/images/smilies/good.gif
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Thanks for your help, I'll let you know how it goes tomorrow.
CNexus said:
Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Thanks for your help, I'll let you know how it goes tomorrow.
Sent from my PG06100
Click to expand...
Click to collapse

Hi, Just wondering if you would mind re-uploading the original files? The link is broken, and I'd really like to unroot my phone, so it would be really appreciated. Thanks heaps!

ASUS ME176C/CX- Unlock Bootloader & Install TWRP

Please note: the information in this thread is out of date. I recommend installing me176c-boot instead, found in https://forum.xda-developers.com/me...tloader-me176c-boot-asus-memo-pad-7-t3780225.
DISCLAIMER: I am NOT responsible for anything that goes wrong with your device. This tablet's very resilient and theoretically unbrickable, but it can still happen.
@social-design-concepts is working on a bootloader "unlock" for all Intel Bay Trail devices running Lollipop. It's working fine on our tablet, so he's given me permission to release the unlock for this device, as well as a TWRP image.
Download the images from here:
https://www.androidfilehost.com/?fid=312978532265362065
UPDATED! TWRP is now version 3.0.2!
MAKE A BACKUP OF ESP AND RECOVERY IN CASE ANYTHING GOES WRONG. YOU'VE BEEN WARNED.
These images aren't in a Nandroid or anything, you'll have to flash them manually via dd.
REQUIREMENTS
ASUS ME176C or ASUS ME176CX with root (duh )
and either-
Terminal Emulator must be installed on the tablet, and given root access
or
Access to a computer w/ ADB installed
INSTALLATION
Download the linked file from above, then unzip them to somewhere on your tablet. This directory will be noted as /path/to/unzipped/zip in this tutorial.
Open up a command prompt and plug in your tablet (if you're on PC) or just launch Terminal Emulator on your tablet.
This first command can be skipped if you're installing this without a computer, but if you're using ADB, then first run
Code:
adb shell
The next steps are universal for both Terminal Emulator and the PC command prompt or terminal.
While we could use tethered TWRP to back up these partitions, it cannot properly back up the ESP, so we'll be backing up the partitions manually. To do so, run the following to get root permission and back up the original recovery and ESP.
Code:
su
dd if=/dev/block/by-name/ESP of=/path/to/unzipped/zip/stock_ESP.img
dd if=/dev/block/by-name/recovery of=/path/to/unzipped/zip/stock_recovery.img
Then, to install:
Code:
dd if=/path/to/unzipped/zip/ESP.img of=/dev/block/by-name/ESP
dd if=/path/to/unzipped/zip/recovery.img of=/dev/block/by-name/recovery
Finally, reboot the tablet to make sure it worked. The ASUS screen should be replaced with an Intel one.
Volume Down + Power will give you an option of either fastboot or recovery, instead of just booting to fastboot like the stock bootloader.

do we still get otas? what happends if the ota contains a uefi update will it become locked again?

Ruben Craveiro said:
do we still get otas? what happends if the ota contains a uefi update will it become locked again?
Click to expand...
Click to collapse
Becouse the firmware update is for unknown reason always included in the esp.img, then the answer is yes no matter how unlogical it is.
P.S anybody still having 16GB whole emmc dd backup? Some guy from my country who doesn't speak English contacted me on PM, he tried to run some KK to LP update from 4pda.ru while already on lollipop. Now he is stuck in Aptio Setup Utlility (lying to him saying it's BIOS ) and so far this seems to be the only option to help him.
P.P.S I have finaly ordered a Y OTG cable from ebay so next month when I get it I can start debugging my debirf-xkiosk running on kali kernel to find out what's the problem.
*EDIT ilogical maybe?
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Why your tutorial can be in general and mine was moved to Q&A? It's unfair :'(

I got this 'Read only file system' message when I tried the first backup.. this shouldn't be happening, right? Presumably the backup failed?
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]_1:/ $ su
su
[email protected]_1:/ # dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd: /recoverystuff/stock_ESP.img: Read-only file system
1|[email protected]_1:/ #

Worked perfectly with your instructions. Used Terminal Emulator on the tablet.
Sent from my K013 using Tapatalk

seamo123 said:
I got this 'Read only file system' message when I tried the first backup.. this shouldn't be happening, right? Presumably the backup failed?
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
adb server is out of date. killing...
* daemon started successfully *
[email protected]_1:/ $ su
su
[email protected]_1:/ # dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd if=/dev/block/by-name/ESP of=/recoverystuff/stock_ESP.img
dd: /recoverystuff/stock_ESP.img: Read-only file system
1|[email protected]_1:/ #
Click to expand...
Click to collapse
Try doing it through Terminal Emulator, see if that helps.

jerbear294 said:
Try doing it through Terminal Emulator, see if that helps.
Click to expand...
Click to collapse
Nah, same result using terminal emulator.. what's wrong I wonder?

seamo123 said:
Nah, same result using terminal emulator.. what's wrong I wonder?
Click to expand...
Click to collapse
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
Mis012 said:
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
Click to expand...
Click to collapse
I wonder why people use ADB for shell when they don't have to

Mis012 said:
Android in it's natire has no real rootfs so writing backup to /customdir/ rather than /sdcard/customdir is not gonnw work. If you "remounted" rootfs rw (not sure if you can remount ramdisk) it would still be all in ram.
Click to expand...
Click to collapse
Oh ok, I'll just move the folder to the sdcard and give it a try..

seamo123 said:
Oh ok, I'll just move the folder to the sdcard and give it a try..
Click to expand...
Click to collapse
@Mis012 is right, either move it to a micro SD and make the path /Removable/MicroSD/recoverystuff or put it on the internal storage and make the path /storage/emulated/0/recoverystuff

jerbear294 said:
@Mis012 is right, either move it to a micro SD and make the path /Removable/MicroSD/recoverystuff or put it on the internal storage and make the path /storage/emulated/0/recoverystuff
Click to expand...
Click to collapse
Seemed to work fine, thanks! Boots up perfectly with the 'Intel' image. How does one get into recovery though? The volume up/down press/let go power button shenanigans for this pad always drove me totally up the wall. Anytime I ever got into stock recovery it was always by accident!
What's the key combo?

seamo123 said:
Seemed to work fine, thanks! Boots up perfectly with the 'Intel' image. How does one get into recovery though? The volume up/down press/let go power button shenanigans for this pad always drove me totally up the wall. Anytime I ever got into stock recovery it was always by accident!
What's the key combo?
Click to expand...
Click to collapse
Volume Down + Power, just like on the stock bootloader.
When you see the Intel screen release Power but keep holding Volume Down. You'll see a screen with a generic warning, then options to go to either fastboot or recovery.

Mis012 said:
Becouse the firmware update is for unknown reason always included in the esp.img, then the answer is yes no matter how unlogical it is.
P.S anybody still having 16GB whole emmc dd backup? Some guy from my country who doesn't speak English contacted me on PM, he tried to run some KK to LP update from 4pda.ru while already on lollipop. Now he is stuck in Aptio Setup Utlility (lying to him saying it's BIOS ) and so far this seems to be the only option to help him.
P.P.S I have finaly ordered a Y OTG cable from ebay so next month when I get it I can start debugging my debirf-xkiosk running on kali kernel to find out what's the problem.
*EDIT ilogical maybe?
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Why your tutorial can be in general and mine was moved to Q&A? It's unfair :'(
Click to expand...
Click to collapse
why just not simply go to dnx mode? then from there make fastboot flash osloader efilinux.efi and then fastboot boot droidboot.img from there it should boot to droidboot and allow to load temp recovery and flash .36(ive already been stuck in uefi for at least 2 times and this method helped me... yesterday i was stuck and its working again)

jerbear294 said:
Volume Down + Power, just like on the stock bootloader.
When you see the Intel screen release Power but keep holding Volume Down. You'll see a screen with a generic warning, then options to go to either fastboot or recovery.
Click to expand...
Click to collapse
That's great, thanks! So does this mean that we're all ready to install a custom ROM when one comes along? Running CM or AOSP on this device would be brilliant, I can finally forget all about that piercing white ASUS ui for a start

seamo123 said:
That's great, thanks! So does this mean that we're all ready to install a custom ROM when one comes along? Running CM or AOSP on this device would be brilliant, I can finally forget all about that piercing white ASUS ui for a start
Click to expand...
Click to collapse
Precisely. A custom ROM is possible with this bootloader.

Ruben Craveiro said:
why just not simply go to dnx mode? then from there make fastboot flash osloader efilinux.efi and then fastboot boot droidboot.img from there it should boot to droidboot and allow to load temp recovery and flash .36(ive already been stuck in uefi for at least 2 times and this method helped me... yesterday i was stuck and its working again)
Click to expand...
Click to collapse
He tried, it complained about some partitions not existing.

Mis012 said:
He tried, it complained about some partitions not existing.
Click to expand...
Click to collapse
he needs to repartition the tablet :
Code:
fastboot oem start_partitioning
fastboot oem partition /system/etc/partition.tbl
fastboot oem format factory
fastboot oem format cache
fastboot oem format system
fastboot oem format config
fastboot oem format logs
fastboot oem format misc
fastboot oem format data
fastboot oem stop_partitioning

Does it work with Build .36?
Hello,
i updated my me176c to the build number WW_V12.10.1.36_20151230 can i use your unlocked bootloader ?

intNERD said:
Hello,
i updated my me176c to the build number WW_V12.10.1.36_20151230 can i use your unlocked bootloader ?
Click to expand...
Click to collapse
you can use the unlocked bootloader on any lollipop version

Ruben Craveiro said:
you can use the unlocked bootloader on any lollipop version
Click to expand...
Click to collapse
Thank You! Great work! Cant wait for a custom rom!

Need Blu Vivo Air LTE Stock ROM!

Anyone know where I can get a stock rom for my Vivo Air LTE?

I have a system.IMG and boot.img
I have a system.IMG and a boot.img if you still need it?

i need it. I accidentally deleted a system/lib file. thought i put it there. I did not... how would I go about installing? I'll google the steps in the mean time.

trentag1988 said:
i need it. I accidentally deleted a system/lib file. thought i put it there. I did not... how would I go about installing? I'll google the steps in the mean time.
Click to expand...
Click to collapse
After downloading system.img to your computer you need to put the vivo air LTE in fastboot mode by turning it completely off. Then hold down power+volume up. Then choose reboot to bootloader connect the phone to your computer. Make sure you have adb and fastboot installed via Android SDK where adb resides such as the platform-tools directory put system.img in that folder and in that folder open it. Right click any white space while holding down shift on your keyboard and click open command from here. Then you can enter fastboot commands. fastboot devices make sure your device is detected then fastboot -w then fastboot format system then fastboot flash system system.img is your recovery still stock? here are three files system.img if your recover is messed too then i include recovery as well im not too sure if you need the boot.img but i included it in this link:
https://drive.google.com/drive/folders/0B4_9-6sS8dFeTGpSLVVSN015STA?usp=sharing
let me know how it goes ok??
---------- Post added 28-09-2016 at 12:10 AM ---------- Previous post was 27-09-2016 at 11:26 PM ----------
I also created a checksum file.chk use ubuntu's md5sum -c file.chk. To check md5

Recovery is still stock. I got 15 second adb installer. Is that the same as android SDK? I'll have to try this tonight. Google drive is requesting that I get permission. Allow when you can. Thank you! I'll attempt this tonight
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
Is it okay that I didn't allow USB debug before bricking?

sorry i dunno if i shared it correctly on my google drive try this
trentag1988 said:
Recovery is still stock. I got 15 second adb installer. Is that the same as android SDK? I'll have to try this tonight. Google drive is requesting that I get permission. Allow when you can. Thank you! I'll attempt this tonight
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
Is it okay that I didn't allow USB debug before bricking?
Click to expand...
Click to collapse
try this link i shared it to all
https://drive.google.com/drive/folders/0B4_9-6sS8dFeTGpSLVVSN015STA?usp=sharing
https://drive.google.com/drive/folders/0B4_9-6sS8dFeTGpSLVVSN015STA?usp=sharing

Downloading now. Can't wait to try!!! Thank you so much. That little phone is surprisingly amazing

here's the kicker though... i tried to 'restart to bootloader', i get stuck on blu splash screen. after getting rid of that one file, it's stayed stuck at blu screen. ever encountered this?

Blu vivo screen
When you are in recovery and reboot into bootloader that's where the Blu vivo air sign is stuck but you can execute fastboot commands

So, I got it to work. I had to terminal fastboot command, then reboot to bootloader, and it finally stuck. You are a life saver.
Was much easier to do in Linux than it was in Windows.

I put it in root with "sudo -s" command then "fastboot install system system.img" do I need to leave the bootloader unlocked??
---------- Post added at 01:42 AM ---------- Previous post was at 01:40 AM ----------
I was thinking of compiling a twrp for this phone, but I'm a little not sure exactly how to do it. I've seen tutorial, but vague

Blu vivo air lte
Alright, that's what I wanted to hear!! Glad you got your phone back...Sux there's no Roms and custom recovery for this phone but at least you got it working glad to have helped!

About the system.img
trentag1988 said:
here's the kicker though... i tried to 'restart to bootloader', i get stuck on blu splash screen. after getting rid of that one file, it's stayed stuck at blu screen. ever encountered this?
Click to expand...
Click to collapse
OK I had to root this vivo air LTE via king root to backup system image so if you want full stock you need to root your phone again with king root and then install super Sume from play store to remove KingRoot and have it replaced with SuperSU. Then you can fully unroot with SuperSU!!! I tried playing Pokemon go and it wouldn't let me because it thought my phone was rooted so that's one way to fix that!

Ohhhhhhh I was wondering how you got the image files ? I haven't had any issues with it so far. It's back to its wonderful goodness. By the way, how do you quote someone on here?? I see everyone doing it, but I don't know how

Quotes
Not too sure