I currently have a rooted HD 7 with TWRP Loaded on the device. If I try to boot into the main OS, My device hangs at the Amazon logo. Is there any way to resture from the Kindle Update file available on the Amazon site, or can anyone help me out with an Image that I can recover from? Nothing I have tried so far has worked, so just looking for some insight/help with the issue
cskimbrell said:
I currently have a rooted HD 7 with TWRP Loaded on the device. If I try to boot into the main OS, My device hangs at the Amazon logo. Is there any way to resture from the Kindle Update file available on the Amazon site, or can anyone help me out with an Image that I can recover from? Nothing I have tried so far has worked, so just looking for some insight/help with the issue
Click to expand...
Click to collapse
What did you do to screw things up? build.prop again? The good thing is that I think it should be very fixable.
In any event, grab 4.5.3 :
https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
If you know which file you screwed up, restore it in TWRP from the above bin (rename to zip, unpack). Replace the file you screwed up with the correct one.
2nd option is to give TWRP this 4.5.3 update zip, and then you can start from Kingroot, and all the fun
3rd option is to be more surgical, in which case you need to disable these 4 lines in updater-script, and delete /recovery in the update zip.
Important!!! if you are editing updater-script in Windows, make sure you are using something like Notepad++ and have your EOL set to Unix type (Edit/EOL conversion).
OK, edit this: 20-4.5.3/META-INF/com/google/android/updater-script
delete
package_extract_dir("recovery", "/system");
package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");
package_extract_file("images/lk.bin", "/dev/block/platform/mtk-msdc.0/by-name/UBOOT");
package_extract_file("images/tz.img", "/dev/block/platform/mtk-msdc.0/by-name/TEE1");
Re-zip, and give it to TWRP. Hopefully this will keep your unlocked bootloader, and TWRP. TWRP should give you an option to install "su", and you are in business.
bibikalka said:
What did you do to screw things up? build.prop again? The good thing is that I think it should be very fixable.
In any event, grab 4.5.3 :
https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin
If you know which file you screwed up, restore it in TWRP from the above bin (rename to zip, unpack). Replace the file you screwed up with the correct one.
2nd option is to give TWRP this 4.5.3 update zip, and then you can start from Kingroot, and all the fun
3rd option is to be more surgical, in which case you need to disable these 4 lines in updater-script, and delete /recovery in the update zip:
this file: 20-4.5.3/META-INF/com/google/android/updater-script
delete
package_extract_dir("recovery", "/system");
package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");
package_extract_file("images/lk.bin", "/dev/block/platform/mtk-msdc.0/by-name/UBOOT");
package_extract_file("images/tz.img", "/dev/block/platform/mtk-msdc.0/by-name/TEE1");
Re-zip, and give it to TWRP. Hopefully this will keep your unlocked bootloader, and TWRP. TWRP should give you an option to install "su", and you are in business.
Click to expand...
Click to collapse
Un-related, but thanks for this. Been looking for a way to restore things a bit without breaking everything
To make things easier, these are some more specific instructions. Download 20-4.5.3 update, unpack it. Replace the script in 20-4.5.3/META-INF/com/google/android/updater-script with my attachment. You can compare the original with my version in Notepad++ (install plugin "compare"), in Linux it's even more trivial.
In addition, delete the following directories/files :
20-4.5.3/recovery
20-4.5.3/images
20-4.5.3/system/priv-app/com.amazon.weather.apk
20-4.5.3/system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
20-4.5.3/system/priv-app/DeviceSoftwareOTA.apk
20-4.5.3/system/priv-app/com.amazon.geo.client.maps.apk
(could delete a few more apk's here to make room in /system )
Zip everything, making sure the paths are the same as in the original Amazon bin. Boot TWRP, and give it this zipped update. It should install in /system, while keeping /data intact. If there are problems, copy the log to SDCard, and post your questions here.
As long as we are not touching the key partitions (recovery, UBOOT, TEE1), things should be safe, and simple to recover in case there are problems. TWRP should let you install "su", then install SuperSu, GAPPS, etc.
At some point we should repackage the known working gapps as a flashable zip file.
Hello guys, I'm actually going through a similar situation but I do not have TWRP installed and cannot pass further recovery since I am in a loop.
Am I able to install TWRP only with recovery access? thanks
bibikalka said:
To make things easier, these are some more specific instructions. Download 20-4.5.3 update, unpack it. Replace the script in 20-4.5.3/META-INF/com/google/android/updater-script with my attachment. You can compare the original with my version in Notepad++ (install plugin "compare"), in Linux it's even more trivial.
In addition, delete the following directories/files :
20-4.5.3/recovery
20-4.5.3/images
20-4.5.3/system/priv-app/com.amazon.weather.apk
20-4.5.3/system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
20-4.5.3/system/priv-app/DeviceSoftwareOTA.apk
20-4.5.3/system/priv-app/com.amazon.geo.client.maps.apk
(could delete a few more apk's here to make room in /system )
Zip everything, making sure the paths are the same as in the original Amazon bin. Boot TWRP, and give it this zipped update. It should install in /system, while keeping /data intact. If there are problems, copy the log to SDCard, and post your questions here.
As long as we are not touching the key partitions (recovery, UBOOT, TEE1), things should be safe, and simple to recover in case there are problems. TWRP should let you install "su", then install SuperSu, GAPPS, etc.
At some point we should repackage the known working gapps as a flashable zip file.
Click to expand...
Click to collapse
Alright. so I followed all your instructions, Copied the created Update.zip file to my Kindle. I go in TWRP and hit Install, and choose the zip inthe /sdcard folder. The Install fails and this is all the log says:
I:Set overlay: ''
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
Iperation_start: 'Flashing'
Installing '/sdcard/Update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/Update.zip'
Updating partition details...
Iata backup size is 0MB, free: 11823MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
Any IDea what or why or any other info I can provide?
cskimbrell said:
Alright. so I followed all your instructions, Copied the created Update.zip file to my Kindle. I go in TWRP and hit Install, and choose the zip inthe /sdcard folder. The Install fails and this is all the log says:
Any IDea what or why or any other info I can provide?
Click to expand...
Click to collapse
Not sure what you are doing wrong, but I just did this yesterday, and everything worked smoothly. I wonder if you are editing the updater script as a Unix file.
In any event, go grab the latest 20-4.5.4 update, and replace the attached "updater-script" in 20-4.5.4/META-INF/com/google/android/updater-script (which worked for me). There is nothing scary about 4.5.4, so might as well restore to this one. My USB drive was UDF (TWRP did not see that), so I had to copy the *zip to the internal storage first. Can this be a source of a problem for you?
In addition, delete the following directories/files :
20-4.5.4/recovery
20-4.5.4/images
20-4.5.4/system/priv-app/com.amazon.weather.apk
20-4.5.4/system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
20-4.5.4/system/priv-app/com.amazon.geo.client.maps.apk
Rename (just in case):
20-4.5.4/system/priv-app/DeviceSoftwareOTA.apk to *apk_
Have jmz tool handy (downloaded), and SuperSu flashable zip (for TWRP). Once your 4.5.4 is up and running, you should flash SuperSu, and then use jmz tool to get GAPPS.
Important: If you have anything other than 4.5.3, I recommend that you flash the 4.5.3 bootloaders separately first before doing any updating business. I've attached the flashable zip with 4.5.3 bootloader as well (uboot*zip).
bibikalka said:
Not sure what you are doing wrong, but I just did this yesterday, and everything worked smoothly. I wonder if you are editing the updater script as a Unix file.
In any event, go grab the latest 20-4.5.4 update, and replace the attached "updater-script" in 20-4.5.4/META-INF/com/google/android/updater-script (which worked for me). There is nothing scary about 4.5.4, so might as well restore to this one. My USB drive was UDF (TWRP did not see that), so I had to copy the *zip to the internal storage first. Can this be a source of a problem for you?
In addition, delete the following directories/files :
20-4.5.4/recovery
20-4.5.4/images
20-4.5.4/system/priv-app/com.amazon.weather.apk
20-4.5.4/system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
20-4.5.4/system/priv-app/com.amazon.geo.client.maps.apk
Rename (just in case):
20-4.5.4/system/priv-app/DeviceSoftwareOTA.apk to *apk_
Have jmz tool handy (downloaded), and SuperSu flashable zip (for TWRP). Once your 4.5.4 is up and running, you should flash SuperSu, and then use jmz tool to get GAPPS.
Important: If you have anything other than 4.5.3, I recommend that you flash the 4.5.3 bootloaders separately first before doing any updating business. I've attached the flashable zip with 4.5.3 bootloader as well (uboot*zip).
Click to expand...
Click to collapse
I am also getting the flash failed message with 4.5.3. Where were you able to grab a copy of 4.5.4?
bibikalka said:
Not sure what you are doing wrong, but I just did this yesterday, and everything worked smoothly. I wonder if you are editing the updater script as a Unix file.
In any event, go grab the latest 20-4.5.4 update, and replace the attached "updater-script" in 20-4.5.4/META-INF/com/google/android/updater-script (which worked for me). There is nothing scary about 4.5.4, so might as well restore to this one. My USB drive was UDF (TWRP did not see that), so I had to copy the *zip to the internal storage first. Can this be a source of a problem for you?
In addition, delete the following directories/files :
20-4.5.4/recovery
20-4.5.4/images
20-4.5.4/system/priv-app/com.amazon.weather.apk
20-4.5.4/system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
20-4.5.4/system/priv-app/com.amazon.geo.client.maps.apk
Rename (just in case):
20-4.5.4/system/priv-app/DeviceSoftwareOTA.apk to *apk_
Have jmz tool handy (downloaded), and SuperSu flashable zip (for TWRP). Once your 4.5.4 is up and running, you should flash SuperSu, and then use jmz tool to get GAPPS.
Important: If you have anything other than 4.5.3, I recommend that you flash the 4.5.3 bootloaders separately first before doing any updating business. I've attached the flashable zip with 4.5.3 bootloader as well (uboot*zip).
Click to expand...
Click to collapse
Tried with the 4.5.4 Update as well. Unfortunately I get the same issue. Log file says
Installing '/sdcard/update-kindle-20.4.5.4_user_454006120.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/update-kindle-20.4.5.4_user_454006120.zip'
Updating partition details...
Iata backup size is 0MB, free: 11822MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
Click to expand...
Click to collapse
TO make sure I'm doing this right.. I just boot into TWRP, Select Install, Select the update fie in my sdcard folder, Then Swipe to Confirm flash.. Right?
Another weird thing i noticed. If I go to Advanced, then Fix Permissions I get "Can't Check Permissions after Factory Reset. Please boot rom and try again after you reboot into recovery" This remains this way any time I reboot into recovery. And of course I cannot do a normal boot as my device hangs at the Amazon Logo when trying a normal boot.
cskimbrell said:
Alright. so I followed all your instructions, Copied the created Update.zip file to my Kindle. I go in TWRP and hit Install, and choose the zip inthe /sdcard folder. The Install fails and this is all the log says:
I:Set overlay: ''
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
Iperation_start: 'Flashing'
Installing '/sdcard/Update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/Update.zip'
Updating partition details...
Iata backup size is 0MB, free: 11823MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
...done
Any IDea what or why or any other info I can provide?
Click to expand...
Click to collapse
cskimbrell said:
Tried with the 4.5.4 Update as well. Unfortunately I get the same issue. Log file says
TO make sure I'm doing this right.. I just boot into TWRP, Select Install, Select the update fie in my sdcard folder, Then Swipe to Confirm flash.. Right?
Another weird thing i noticed. If I go to Advanced, then Fix Permissions I get "Can't Check Permissions after Factory Reset. Please boot rom and try again after you reboot into recovery" This remains this way any time I reboot into recovery. And of course I cannot do a normal boot as my device hangs at the Amazon Logo when trying a normal boot.
Click to expand...
Click to collapse
I kind of think that perhaps your /data partition is screwed up. "sdcard" sits somewhere there as well. Do you have an OTG cable? If you don't, it can be tricky, since you have no way to send files to the TWRP. Otherwise you could just reformat /data in TWRP, and make sure that /media or whatever is also reformatted. I reformatted /data yesterday, and did recall some weird messages, but my OS was fine. So I just blasted through, and it re-created stuff in /data.
bibikalka said:
I kind of think that perhaps your /data partition is screwed up. "sdcard" sits somewhere there as well. Do you have an OTG cable? If you don't, it can be tricky, since you have no way to send files to the TWRP. Otherwise you could just reformat /data in TWRP, and make sure that /media or whatever is also reformatted. I reformatted /data yesterday, and did recall some weird messages, but my OS was fine. So I just blasted through, and it re-created stuff in /data.
Click to expand...
Click to collapse
I'll give a try to formatting those partitions. I assume using the "Wipe" command on them formats them? (Forgive my ignorance.. Im still new to using TWRP and such.. I work on computers for a living and this ordeal is driving me nuts.. hah)
I do not have an OTG Cable, So far I have been pushing files directly to the Kindle from my laptop with the Android File Manager, and then moving them around on the device from the advanced File Manager on TWRP. Would an OTG Cable do anything different than what I am already doing other than simplify it?
Im just not sure if I have files in the right place when I go about flashing them, or if that even matters.
cskimbrell said:
I'll give a try to formatting those partitions. I assume using the "Wipe" command on them formats them? (Forgive my ignorance.. Im still new to using TWRP and such.. I work on computers for a living and this ordeal is driving me nuts.. hah)
I do not have an OTG Cable, So far I have been pushing files directly to the Kindle from my laptop with the Android File Manager, and then moving them around on the device from the advanced File Manager on TWRP. Would an OTG Cable do anything different than what I am already doing other than simplify it?
Im just not sure if I have files in the right place when I go about flashing them, or if that even matters.
Click to expand...
Click to collapse
Indeed, explore TWRP a bit. I guess you can sideload with TWRP, so it does not matter. But notice the update will wipe /system, so you cannot have your zip there. Otherwise it won't care too much, it'll just unpack it into its destination. As long as you are not touching your recovery, and the bootloader, you should be fairly safe.
bibikalka said:
Indeed, explore TWRP a bit. I guess you can sideload with TWRP, so it does not matter. But notice the update will wipe /system, so you cannot have your zip there. Otherwise it won't care too much, it'll just unpack it into its destination. As long as you are not touching your recovery, and the bootloader, you should be fairly safe.
Click to expand...
Click to collapse
..................... Well... I figured out my problem.......
Like a moron.. I was zipping up the Folder all the update files were in.. and not the actual collection of files.....
Sigh...... I know better than this.... haha...
Related
A few weeks ago my SD card went bad on me. I have been using Gingershedbread as my ROM and see there are some updates, however, since I don't have an SD card, the "normal" method of loading the zip onto the SD card obviously won't work for me.
My question is: Is there a way to flash a ROM zip from a pc (windows) to my phone without an SD card? I know you can put the zip on the data partition, then use "recovery --update_package=DATA:rom.zip" (through adb), however, when trying to copy the rom I get a message saying that there is no space left.
As of now, the only thing I know of is to do a full wipe and factory reset, then push the ROM zip to my phone, but I don't necessarily want to do this every time.
I have also tried fastboot and using mkyaffs2image to create a system.img from the ROM's system folder in the zip file, but I am not doing something right.
I run "mkyaffs2image c:\rom\system\ c:\system.img"
then with my phone in fastboot, I "fastboot flash system c:\system.img"
and "fastboot flash boot c:\rom\boot.img".
I restart the phone in recovery mode, load gapps and xtrCache, but then it reboots, sits on black screen for a few seconds, then reboots into recovery.
I have tried erasing system and boot first, but that didn't seem to help.
I first tried just flashing system.img, but that didn't work.
Not sure what I am doing wrong. Is there a way to take a ROM zip and create a system.img and boot.img that can be flashed through fastboot without an SD card? OR, is it possible to flash a ROM zip without transferring the file to my phone first? Any help would be appreciated.
I don't think that there is an answer to your question which is both complete and also short.
So, here goes with the long answer.
First, a yaffs2 image file (e.g. system.img) is not compressed, so it is quite large - for things like the HTC factory/stock ROMs, it can be bigger than the cache partition. I don't know if the cache partition is actually used when you push things with fastboot, but experimentally, I have run into the problem that when attempting to do a
Code:
fastboot flash system my-yaffs2-system.img
fastboot gives you get an error about being out of room.
Second, and more importantly, the file modes (permissions) and user:group ownership of files in the /system mount point are extremely critical to proper operation of Android. If you have files sitting on a Windoze machine filesystem (either FAT32 or NTFS), all this information will be lost even before you create your "yaffs2" image file. (Not only that, but all symbolic links will be missing, too). This is why you observe that ROM files have instructions in their "update-script" (or "updater-script") command files for setting file & directory ownership, file permission modes, creating symlinks, et cetera.
Third - even if you use a linux OS to unpack yaffs2 images, and run as root when you are doing so, a lot of the "unyaffs" programs that are lying around do not even bother to extract things like user:group ownership or file modes - so you are basically screwed as soon as you unpack a yaffs2 image file on a PC, no matter whether it is Windows or Linux/Unix/OS-X.
Fourth, I am not sure that it is even a good idea in the first place to be "flashing" yaffs2 images. The "fastboot flash" command merely writes whatever you pass to it as a long linear blob of bytes, and there is no evidence to suggest that the yaffs formatting used in the archive is the same formatting used by the kernel. When "Nandroid" runs to restore a system.img or data.img file onto the phone, it does not write the image as a linear blob of bytes: it actually mounts the filesystem in question, cleans it up with a "rm -rf *" command, and then manually unpacks the yaffs2 image file into the mounted file system, one file at a time. (Fortunately in this case, it actually restores things like symlinks, file permissions, and file/directory user:group ownership information). This insures that the low-level yaffs2 formatting is *identical* to what the kernel expects, because it is the kernel that creates it.
There is a solution, but it is tedious enough that you really ought to ask the question, "Why don't I go out and buy a replacement SD card for 10 bucks instead of wasting a huge amount of time?"
Here's the solution:
You mount /system, clean it up manually, use adb to push the files recursively from wherever you have them stored on your PC, and then afterwards you run a custom (signed) installer .zip file which has been modified so that it only contains the "symlink" and permission-setting commands - you delete the "format" and "extract" commands from that command file, since you have manually put all the files into /system. Either that or you manually adjust the permissions and user:group ownership information by hand.
Obviously, since you don't have an /sdcard any longer, you will need to put this flashable, custom .zip file in /cache, and then create a one-line command file at /cache/recovery/command that points at the flashable .zip file in /cache. (This is the way the the OTAs work, and also how ROM Manager is able to customize the recovery when it boots).
Is this a lot of work? Yeah, you betcha.
It seems like running down to wally world to get a cheap SD card might be a little more fun.
Thanks for the info. I figured getting a new SD would be the best solution.
I knew about the symlink and file permission stuff and was trying to flash a system img then run a zip to ser that info., but couldn't get it to work. Sounds like using fastboot might be a bad idea.
For now I think I will just have to find a rom and stick with it for a while.
I am nearing an upgrade for a new phone and looking at the Thunderbolt, which comes with an SD so I don't want to buy one just yet.
Thanks for your help.
Sent from my ERIS GSBv2.1 using XDA App
kgunnIT said:
then run a zip to ser that info., but couldn't get it to work.
Click to expand...
Click to collapse
If you know how to sign ROMs, it's really not a hard hack to launch an installer of the type you mention.
And, now that I've just said that, I think I have another, simpler, idea.
But first:
[SIZE=+2]How To Launch a (smallish) .zip-based Flash That's Not On the SD Card.[/SIZE]
All of the recoveries - both the stock and custom recoveries - look for a "command" file when they first start up.
It literally is named "command", i.e.: /cache/recovery/command
... and it is a simple text file with as few as one line(s) in it.
Here is an example from the most recent OTA of the contents of /cache/recovery/command:
Code:
--update_package=CACHE:8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
basically, it's just a single line with the following format:
--update_package=CACHE:filename.zip
So, if you are trying to get an installer to run without an SD card, you would:
1) Boot to Amon_RA
2) Wipe the cache if necessary (wipe -> wipe data/factory reset also clears /cache)
3) Push your zip file to cache:
Code:
adb push mycustominstall.zip /cache/
4) Create a command file (say, named "command.txt") with the contents:
Code:
--update_package=CACHE:mycustominstall.zip
5) Push it to the phone:
Code:
adb push command.txt /cache/recovery/command
6) reboot directly back into recovery with
Code:
adb shell reboot recovery
When the recovery boots up again, it will immediately start unpacking your "mycustominstall.zip" file.
After I thought this all the way through, I realized, though: a lot of the ROM files are only about 100 MB, and cache is about 128 Mb, so
.... wait for it .....
... wait for it ....
it might be a worthwhile experiment to just push an untouched ROM file right to cache and then use that ROM file's name in your "command" file.
So long as /sbin/recovery does not unpack files to /cache (I can't remember if it does this or not!), you could use original ROM files -- just what you wanted originally. If it unpacks things to cache, though, it will only get part way through the install and fail.
It's worth a shot; if it fails, you'll have a mess that is no worse to clean up than what you've presently got. (If it fails, to be on the safe side it might be wise to go in using adb and clean things up in /cache a little bit so that the next recovery boot has some wiggle room in /cache - e.g. "adb shell rm -rf /cache/*" )
bftb0
bftb0 said:
If you know how to sign ROMs, it's really not a hard hack to launch an installer of the type you mention.
And, now that I've just said that, I think I have another, simpler, idea.
But first:
[SIZE=+2]How To Launch a (smallish) .zip-based Flash That's Not On the SD Card.[/SIZE]
All of the recoveries - both the stock and custom recoveries - look for a "command" file when they first start up.
It literally is named "command", i.e.: /cache/recovery/command
... and it is a simple text file with as few as one line(s) in it.
Here is an example from the most recent OTA of the contents of /cache/recovery/command:
Code:
--update_package=CACHE:8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip
basically, it's just a single line with the following format:
--update_package=CACHE:filename.zip
So, if you are trying to get an installer to run without an SD card, you would:
1) Boot to Amon_RA
2) Wipe the cache if necessary (wipe -> wipe data/factory reset also clears /cache)
3) Push your zip file to cache:
Code:
adb push mycustominstall.zip /cache/
4) Create a command file (say, named "command.txt") with the contents:
Code:
--update_package=CACHE:mycustominstall.zip
5) Push it to the phone:
Code:
adb push command.txt /cache/recovery/command
6) reboot directly back into recovery with
Code:
adb shell reboot recovery
When the recovery boots up again, it will immediately start unpacking your "mycustominstall.zip" file.
After I thought this all the way through, I realized, though: a lot of the ROM files are only about 100 MB, and cache is about 128 Mb, so
.... wait for it .....
... wait for it ....
it might be a worthwhile experiment to just push an untouched ROM file right to cache and then use that ROM file's name in your "command" file.
So long as /sbin/recovery does not unpack files to /cache (I can't remember if it does this or not!), you could use original ROM files -- just what you wanted originally. If it unpacks things to cache, though, it will only get part way through the install and fail.
It's worth a shot; if it fails, you'll have a mess that is no worse to clean up than what you've presently got. (If it fails, to be on the safe side it might be wise to go in using adb and clean things up in /cache a little bit so that the next recovery boot has some wiggle room in /cache - e.g. "adb shell rm -rf /cache/*" )
bftb0
Click to expand...
Click to collapse
You always find the one thousand and ONETH way to skin a cat. Hehehehe...
Thankyou so much for this this alowed me to flash a rom on my phone which can't detect any sd cards and i stupidly wiped it before relising the sd card wasnt being detected!
sum_guy55 said:
Thankyou so much for this this alowed me to flash a rom on my phone which can't detect any sd cards and i stupidly wiped it before relising the sd card wasnt being detected!
Click to expand...
Click to collapse
very good, sum_guy55!
At least all that typing wasn' t in vain.
Out of curiosity, how big was the ROM file you used?
bftb0
Been meaning to post this:
Thanks for your posts roirraW "edor" ehT and bftb0 for posting this. I also was able to clear the cache and push the ROM and update.
However, I have xtrCMCache2cache on my phone, so the dalvik-cache was moved from /data/ to /cache/. After doing a wipe of dalvik-cache from Amon recovery, the folder in /cache/ was not emptied out. I went ahead and cleaned it manually, which freed up enough space to push the ROM.
Is this behavior expected using cache2cache and wiping dalvik-cache from recovery? I guess it would be since the dalvik-cache was moved.
Anyway, after clearing the dalvik folder, I was able to push GSBv2.4 to my phone, as well as gapps and xtrCMCache2cache, a total of almost 80 MB. Rebooted and all was well.
Thanks again for your help.
kgunnIT said:
Been meaning to post this:
Thanks for your posts roirraW "edor" ehT and bftb0 for posting this. I also was able to clear the cache and push the ROM and update.
However, I have xtrCMCache2cache on my phone, so the dalvik-cache was moved from /data/ to /cache/. After doing a wipe of dalvik-cache from Amon recovery, the folder in /cache/ was not emptied out. I went ahead and cleaned it manually, which freed up enough space to push the ROM.
Is this behavior expected using cache2cache and wiping dalvik-cache from recovery? I guess it would be since the dalvik-cache was moved.
Anyway, after clearing the dalvik folder, I was able to push GSBv2.4 to my phone, as well as gapps and xtrCMCache2cache, a total of almost 80 MB. Rebooted and all was well.
Thanks again for your help.
Click to expand...
Click to collapse
It was all bftb0. Interesting, I had once asked if cache was definitely wiped from Amon after it was moved. The consensus was that it should. I shall be anticipating some light shed on this.
Sent from my Gingerbread Eris via Tapatalk
Well, Amon_RA has no idea whether you are using cache2cache; I suppose we would need to look at the code to figure out how it behaves.
If it mounts /data and then does something like
rm -rf /data/dalvik-cache
there is a chance that the symbolic link is not followed, which would explain what kgunnIT observed.
Normally, if you are flashing a new ROM in a full-wipe fashion, the " wipe data/factory reset" menu option clears both /data and /cache, so in that case it is irrelevant that the "wipe dalvik-cache" is a no-op.
If you are overflashing, it's not obvious that you need to wipe the dalvik-cache... at least for the market apps normally stored in /data/app, although it seems like it would be a good idea to do so, as the system apps could be changing.
Note that even when cache2cache is not in use, the Amon_RA menu item "wipe dalvik-cache" never works as intended for froyo & gingerbread ROMs - the system apps have their dalvik-cache stored in /cache, and this never gets touched by Amon_RA with that menu operation.
BTW... for what it's worth, the ClockworkMod recoveryhas a menu entry for wiping only the cache.
bftb0
bftb0 said:
BTW... for what it's worth, the ClockworkMod recoveryhas a menu entry for wiping only the cache.
bftb0
Click to expand...
Click to collapse
Does ClockworkMod recovery work ok on the Droid Eris? I was going to load it on, but saw some people posting that it bricked their phones, so now I am skeptical. I will do more research and see if this is something I want to do. Thanks for your insight.
kgunnIT said:
Does ClockworkMod recovery work ok on the Droid Eris? I was going to load it on, but saw some people posting that it bricked their phones, so now I am skeptical. I will do more research and see if this is something I want to do. Thanks for your insight.
Click to expand...
Click to collapse
There is a version of Amon_RA (the trackball-optional version) that also allows you to format cache. You can find out more about it here: http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
That said, if you have ROM Manager, you can have Clockwork Recovery start as a stub within Amon_RA just from ROM Manager (the first option copies a file called update.zip to the root of your SD card, and the second, "Reboot into Recovery", starts Amon_RA with a script to flash update.zip, which starts Clockwork.) In fact, once update.zip is on the SD card, you can start Amon_RA as you always do, go to the Flash a zip from SD card menu, choose update .zip, and it will start Clockwork, if you want to do it that way. However, the drawback to this is that you can't go back to Amon_RA without shutting down the phone and then restarting in Recovery again, so I just find it easier to use the trackball-optional version of Amon_RA.
I think every person who has bricked their Eris while running Clockwork was running Clockwork Recovery as their main recovery image, and not in the way that I described in the last paragraph. (Though don't hold me to that ...)
kgunnIT said:
Does ClockworkMod recovery work ok on the Droid Eris? I was going to load it on, but saw some people posting that it bricked their phones, so now I am skeptical. I will do more research and see if this is something I want to do. Thanks for your insight.
Click to expand...
Click to collapse
I've been using it through ROM Manager since last August or so, I use it all the time.
My Atrix 4g has the boot loader unlocked, rooted, is currently running nottachtrix 1.3 with faux 1.3 kernal.
Before flashing nottachtrix I used Clockworkmod Rom Manager to back up the stock rom.
I tried to restore to the stock rom from the app and it failed, the error was "couldn't open directory. no files found" but by this point it had already removed the existing rom. I installed nottachtrix again with out wiping anything and managed to get the phone back working again as before.
I can't restore any of my backups, even new backups made don't work. The error I'm getting is:
"clockworkMod recovery v5.0.2.0
couldn't open directory.
no files found"
The files are still there in the folder /sdcard /clockworkmod/backup the new backups made are also saved to that folder.
From the report.log:
ui_print("ROM Manager Version 5.0.3.1");
ui_print("13 December 2012");
assert(restore_rom("/sdcard/clockworkmod/backup/Stock_backup", "boot", "system", "data", "cache", "sd-ext"));
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.0.3.1
13 December 2012
Checking MD5 sums...
boot.img: OK
cache.ext3.tar: OK
data.ext3.tar: OK
recovery.img: OK
system.ext3.tar: OK
.android_secure.vfat.tar: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/Stock_backup/system.ext3.tar
Restoring system...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk0p12: 11/81920 files (0.0% non-contiguous), 20633/327680 blocks
loads of random code then.
write error: No space left on device
libaudioflinger.solibstlport.solibui.solibbluetooth.solibsensortest.solibz.solibnvomxilclient.solibstagefright.solibpanorama_jni.solibnvmm_video.solibopencore_mp4local.solibmedia_jni.solibhwmediarecorder.solibctest.solibCamera_gingerbread.solibjni_nwp.solibext2_profile.solibrs_jni.solibsurfaceflinger.solibflashplayer.solibysshared.solibstagefright_froyo.solibstagefright_honeycomb.solibaudio.solibjni_latinime.solibphotoflow.solibnvddk_aes_user.solibdlnasysjni.solibSR_AudioIn.solibpppd_plugin.solibgui.solibnvodm_imager.solibwebcore.solibreverbwrapper.solibbundlewrapper.solibvisualizer.solibsrec_jni.solibcrypto.solibnvrm_channel.solibRS.soError while restoring /system!
result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/Stock_backup", "boot", "system", "data", "cache", "sd-ext")
It says "No space left on device" does that mean on the SD Card or the internal storage? There is 1.02 gb available on the internal storage and 3.35 gb on the sdcard how much is required?
Any help would be very much appreciated!
Jonnym
try placing a folder inside your internal storage naming it just like the cwm recovery folder on your sdcard and with the same structure (clockworkmod/backup/ )put your backup inside , and free some space on your internal storage aswell , then try again i remember reading something about different storage settings for different roms
Sent from the gray stuff inside my skull
demonoid phenomenom said:
try placing a folder inside your internal storage naming it just like the cwm recovery folder on your sdcard and with the same structure (clockworkmod/backup/ )put your backup inside , and free some space on your internal storage aswell , then try again i remember reading something about different storage settings for different roms
Sent from the gray stuff inside my skull
Click to expand...
Click to collapse
Thanks for the reply
Last night I uninstalled CWM and reinstalled it then tried it again, it failed when restoring the backup of the stock rom, but it did restore a old back up of nottachtrix.
I updated CWM sometime after backing up the stock rom, I wonder if that's the problem? Or the backup is corrupt, I have a back up of it on the PC so will try using that instead.
What do you think?
Thanks again for the advice.
Jonnym
Jonnym said:
Thanks for the reply
Last night I uninstalled CWM and reinstalled it then tried it again, it failed when restoring the backup of the stock rom, but it did restore a old back up of nottachtrix.
I updated CWM sometime after backing up the stock rom, I wonder if that's the problem? Or the backup is corrupt, I have a back up of it on the PC so will try using that instead.
What do you think?
Thanks again for the advice.
Jonnym
Click to expand...
Click to collapse
agreed, maybe it's an incompatible backup, or also try selective restore option, and restore partition by partition, make sure to do all necessary wipes
Sent from the gray stuff inside my skull
demonoid phenomenom said:
agreed, maybe it's an incompatible backup, or also try selective restore option, and restore partition by partition, make sure to do all necessary wipes
Sent from the gray stuff inside my skull
Click to expand...
Click to collapse
I'm guessing that's all done in Clockworkmod?
Is there any where I can get an older version of Clockworkrom?
thanks for the help
Jonnym
Jonnym said:
I'm guessing that's all done in Clockworkmod?
Is there any where I can get an older version of Clockworkrom?
thanks for the help
Jonnym
Click to expand...
Click to collapse
Thats not a good idea, you risk a hard brick, or need to rsd flash rom again, im not sure about this but there is an adb way to manually flash each partition regardless of restore being corrupt or not but thats too riskiest
Sent from the gray stuff inside my skull
Hi Guys,
I'm hoping someone can help me here with unbricking my daughters Nabi 2 tablet.
The long story short is that I've tried to update to the latest OTA with TWRP 2.3.3.0 (Nabi 1.9.37) and gapps installed in the past (in order to have google play services).
After downloading the OTA and successfull file verification it booted into TWRP mode and this is when things went wrong...
As I wasn't sure about how to even leave the TWRP mode I have hit few things by accident (I think one of them asked me if I want to wipe my ROM and I said YES + when I was after that trying to reboot the tablet it gave me a warning saying something like "you have no OS installed - are you sure to reboot?).
Now, of course due to my stupid actions it doesn't work - stuck on Nabi boot logo and when I try to pres Volume+ and Power together it gives me the screen with 4 options to choose from (Boot Normally, Fastboot Protocol, Recovery Kernel, Forced Recovery) but I still can't select/move the highlighted item. All what I'm able to do now is to power it off by holding the power button pressed for couple seconds.
Based on your experience here - is there anything that can be done or is it a "real brick" and we need to buy something new for her?
Thank you for any suggestions.
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
termostat1000 said:
Hi,
I managed to boot into TWRP somehow...
Could someone please direct me how I can re-flash it with a Nabi 2 UK OS (and where I can source the file from if possible at all)?
Cheers,
T1000
Click to expand...
Click to collapse
Try sections 9 and 10. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
termostat1000 said:
Hi,
Using NabiLab I managed to load stock 1.9.37 through TWRP.
At the moment tablet will start, let me through the initial setup wizard and go into normal mode from when it was new (no Google services available).
When I try to install gapps (TWRP mode) using NabiLab it goes into endless boot loop showing just a splash screen of the screen lock and reloads again.
I tried also bringing it more to factory condition but it is not recognised in NabiLab when android is fully booted (even though PC can see it). I tried different drivers but without too much luck. When in TWRP mode it comes up as Alcatel ADB Device and when adroid is booted it comes up as a storage device rather than ADB.
I feel I'm pretty close but I need just a hint how to solve it finally without bricking it for real...
Cheers
T
Click to expand...
Click to collapse
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
aicjofs said:
Pretty hard to brick a Nabi2.
Why did you choose 1.9.37? Isn't the latest 2.3.2 and already has Gapps?
When in Android do you have ADB turned on in Developer options?
Is this the procedure you used?
a) Download the ROM for your device in section 10
b) Boot to TWRP (see above for instructions)
c) Do a backup of just the boot partition in TWRP.
- Click Restore tab
- Just check "boot" and nothing else.
- Swipe to Backup
d) Eject the external SD from the tablet and place in the computer
- Note: You should unmount the card from the mount tab in TWRP before ejecting it. (Uncheck the box next to external SD)
e) Connect the SD card to you computer
f) On the SD card navigate to the folder TWRP/BACKUPS/XXXX. XXX is a serial number unique to your Nabi.
g) Make a new folder and call in whatever you want. So it should now look like TWRP/BACKUPS/XXX/yourfolder
h) Unzip the ROM file you downloaded in to the "yourfolder" you created above. The files should look like ext4.system.win, emmc.boot.win, ext.addon.win, etc. Inside the the "yourfolder" directory.
i) Download the bootloader zip for your device from section 10
j) Copy it to the external SD in a location you will remember. This will be for the bootloader update.
k) Eject the SD card from your computer (safely eject it)
l) Install SD card in Nabi
- After inserted in tablet go to TWRP mount tab and check the box to mount the SD card
m) Go to restore tab, and find the backup under the "yourfolder" you made and unzipped the files to.
n) You should be able to select boot, system, and addon and skip the others.
o) If everything restores then go to TWRP install tab, find the bootloader.zip you downloaded and install it.
p) Reboot
Code:
[U][B]Nabi2 Original United Kingdom (NABI-NV7A-UK)[/B][/U]
Version 2.3.2[URL="https://www.androidfilehost.com/?fid=24269982087011751"] Download[/URL]
ROM Mirror[URL="http://www.nabtabhacks.com/downloads/232UKstock.zip"] Download[/URL]
Bootloader [URL="https://www.androidfilehost.com/?fid=24269982087013995"] Download[/URL]
Click to expand...
Click to collapse
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
termostat1000 said:
Hi aicjofs,
I followed the steps above except step c which I haven't done.
So it looked good with the NabiLab built in 1.9.37 and it seemed to load fine with my TWRP 2.3.3.0 but it was hgoing into this endless boot loop after trying to install gapps. BTW I went for 1.9.37 as it came with NabiLab and turned right.
After your reply I've donwloaded the 232UK stock rom and bootloader. Copied both onto SD card - at that stage it would let me do a restore directly from the SD card so I've copied the 232UK rom into internal memory. Restore process went OK and at the end I've installed its dedicated bootloader...
Right now the situation is that I can only boot into TWRP but restore doesn't show any available roms (both internal or external memory) even though there is backup folder on the SD card.
What worries me the most is when I go to advanced / file manager / sdcard (internal memory) in TWRP mode it doesn't show any files or folders there. When I try to dipslpay tablet information in NabiLab it shows the external SD card properties properly (capacity/free space) but on the internal memory it says "Size df:KB Free can'tKB used find".
Does it mean it has wiped all the internal memory down to zero? Would this be the reason for recovery no being able to identify the roms on external SD card too?
Looking at the log in TWRP mode it is filled with entries like
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Can't open /cache/recovery/last_install
E:Can't open (No such file or directory)
What a pain is this thing, honestly...
Click to expand...
Click to collapse
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
aicjofs said:
My fault. I forgot to tell you once you update the bootloader you need to use TWRP for Jellybean, you are still using TWRP for Ice Cream Sandwich .
Code:
[B][U]Nabi2 Original (NABI-NV7A)[/U][/B]
Ice Cream Sandwich TWRP 2.6.3[URL="http://forum.xda-developers.com/attachment.php?attachmentid=2586828&d=1392743412"] Download[/URL]
Jellybean TWRP 2.8.5[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3211498&d=1426404068"] Download[/URL]
KitKat TWRP 2.8.7[URL="http://forum.xda-developers.com/attachment.php?attachmentid=3473994&d=1442276115"] Download[/URL]
Discussion Thread [URL="http://forum.xda-developers.com/showthread.php?t=2074501"]Link[/URL]
At that point you can try to restore the 2.3.2 ROM again. Or try the 2.2 ROM http://forum.xda-developers.com/showpost.php?p=50341726&postcount=85
Click to expand...
Click to collapse
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
termostat1000 said:
Forgive me please but I'm not entirely sure how to load this TWRP 2.8.5 for JellyBean on it with TWRP 2.3.3.0 in place..
Cheers
Click to expand...
Click to collapse
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
aicjofs said:
You will need to use fastboot to load it. If you have a nabilab folder it already has fastboot available. So using the procedure below you couldn't download the ZIP file I linked in post above. Extract the from the zip the recovery.img or twrp-recovery.img and put it in the nabilab folder. (Im puling the procedure from http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 )
1) To load TWRP we will be in the fastboot operational mode(see section 3)
Device powered off:
-Depending on device press and hold the power and vol - keys OR power and vol + key. Some will boot straight to recovery, and others will come to the "bootloader" screen. We want the bootloader.
-To enter fastboot use vol+ and vol- to highlight and select fastboot protocol. (Device will need to be plugged in to computer and fastboot driver installed before the screen will change)
Device powered on:
-Use ADB and execute from the command line:
Code:
adb reboot-bootloader
2) USB plugged in and Fastboot/Bootoader Driver loaded(see section 4) verify with windows device manager if needed.
3) Download the TWRP zip file for your device from TWRP list below(see section 8)
4) Extract the file to the location your are running your command prompt(see section 6)
-The file will be called twrp-recovery.img or recovery.img
5) Depending on the name of the file in step 4, load TWRP by typing at the command prompt:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery twrp-recovery.img
Click to expand...
Click to collapse
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
termostat1000 said:
Hi,
Thank you very much for your help but it clearly looks that this is way beyond my knowledge on how to use all of these fastboot, command, adb and so on...
I regret I ever touched the thing at all.
So there is absolutely no easy way - command line is a must from where I am right now?
Click to expand...
Click to collapse
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
aicjofs said:
Its not a must but easiest to try and walk you through. Which version of Nabilab are you using? You could move some files around and still use Nabilab. Up to you which way to go forward. I'll try and help.
Click to expand...
Click to collapse
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
termostat1000 said:
Hi,
I'm not so much afraid of copy/paste for cmd... the biggest fear is that I don't know anything about ADB, fasboot etc. So when your instruction in previous post says use ADB and I purely don't know what it means.
I think if the option is there I'd like to ask if you could help with restoring it with Nabilab.
Thanks a million for your help!
T
Click to expand...
Click to collapse
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
aicjofs said:
Which version of Nabilab are you using? Is it the commandline version. Black window, where you have to use keyboard to make selections?
Click to expand...
Click to collapse
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
termostat1000 said:
Hi,
I'm using Nabilab ver 2 - black windows with keyboard made selections.
Click to expand...
Click to collapse
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
aicjofs said:
Find the Nabilab folder on your computer. Open the "recovery" folder. Then open the "stock" folder. Inside it there is recovery.img file. Rename it to recoverystock.img.
You downloaded the twrp-recovery-JBNV7AUS.zip from a few posts back. Extract the twrp-recovery.img file and put it in the stock folder. Now rename the twrp-recovery.img file to recovery.img.
Now boot the tablet to TWRP recovery(the one that isn't working) and run Nabilab. Select 4 Install recoveries. Then 4 instal stock recovery. Then reboot in to recovery and see if you have the 2.8.5 recovery
Click to expand...
Click to collapse
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
termostat1000 said:
Great!
Your trick worked fine and now I can see TWRP 2.8.5.0 and I have problems with drivers - keeps failing to recognize the tablet.
I'll work on the driver issue or is there something I should know about it with TWRP 2.8.5.0 lodaed?
What is my next step from here as Android is still stuck on Nabi logo (no motion) and I'm afraid to do anything in case I create even bigger mess than I already have
I also noticed when I try to shut it down from inside TWRP it asks me a question if I want to root the tablet (Install super SU) - is it something I should do and at what stage?
Thanks!
T
Click to expand...
Click to collapse
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
aicjofs said:
If you can see the files again now with the correct TWRP. You can try to restore the 2.3.2 ROM again. Or maybe try the procedure from post #5 with the 2.2 ROM I linked to in post #7. You don't have to do the bootloader install anymore so skip that step. Installing root doesn't matter, you can choose to install or not.
Click to expand...
Click to collapse
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
termostat1000 said:
You're a STAR!
All happy working as new with 232UK ROM and bootloader loaded with your instructions.
I'd never get this sorted without your specialized help.
If I only could I'd send you something just to say Thank You...
T - Happy Dad of Amelia
Click to expand...
Click to collapse
Your thanks is enough Glad we got it sorted and a happy kid!
Hey everyone,
A few days ago, I decided to downgrade from AICP 11 back to 10 (Android 6.0.1 to 5.1.1), wiped everything but internal storage. When flashing, I got an error, saying that the /vendor partition was missing, and indeed, while it existed, I could only mount it forcefully, because the device was busy.
This lead to a complete wipe, as after a reboot, TWRP asked for an encryption password, which I didn't set. Here, I did a factory reset & wiped everything. After that, I tried flashing again (5.1.1), but after it was completed, I got a line, which said "Couldn't unmount /system", which is true, as it's already unmounted. But when I mount it, all the files that are supposed to be installed seem to be there.
When I reboot the device, it gets stuck on the Google logo.
Frankly, I'm afraid to even flash back to stock, so I was hoping that someone more experienced could help me out.
It should be noted, that I still have access to fastboot, and TWRP.
Thanks in advance,
DecentM
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
dmantilal said:
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
Click to expand...
Click to collapse
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
DecentM said:
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
Click to expand...
Click to collapse
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
dmantilal said:
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
Click to expand...
Click to collapse
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
DecentM said:
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
Click to expand...
Click to collapse
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
dmantilal said:
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
Click to expand...
Click to collapse
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back on how it went.
DecentM said:
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back how it went.
Click to expand...
Click to collapse
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
dmantilal said:
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
Click to expand...
Click to collapse
I don't think that the issue is with the vendor image anymore, but with the partitions in general. I always had a mismatched vendor image, as it only results in a modal box after boot.
My problem is again, with the /system partition not being visible to flashable zip files.
Mismatched vendor.img can also cause bootloops and other quirks like battery-charge percentage inaccuracies.
Every time I try to install a custom rom, my device gets bricked. I'm stuck in a bootloop and TWRP tells me, that /data is unusable and /system can't be unmounted.
Right now I get I back to life, if I change the filesystem in TWRP for /data from f2fs to ext4 and back. After that /data is empty, but usable again. To get /system back to work, I erase it with "fastboot erase system". Then I reboot TWRP and reinstall STF-L09 8.0.0.360(C432) with zxz0O0s HuRUpdater. The logfile for the installation is attached with the title "Log during installation.zip".
After the installation I do a reboot and go through all the setup stuff of Android (WLAN, do you want to use..., etc.). Then everything seems to work fine. I can use the phone and reboot without a problem. But if I start TWRP, there are error messages about it can't unmount /system. I attached that logfile with the title "Log after Installation.zip". If I try to install an OTA update it gets bricked again.
No matter, how I try to install the custom rom, or how I reset my phone after it gets bricked, seems to make a difference. To me it seems like, either a problem with the file system, or a driver problem. But I'm not sure, because I'm more experienced with PCs. If I would have such a problem with a PC, I would erase everything and do a fresh start. But I don't know how to handle this here.
Please help me, to get out of this bricking cycle, before I can build a wall.
Status Update 1:
I went back to STF-L09C432B120 (Android 7) with this method: https://forum.xda-developers.com/showpost.php?p=75084955&postcount=17
All credits to gaguga:
Rollback from 8 android to 7
1. Place the firmware files of ?any? android 7 update.zip, update_data_public.zip and update_all_hw.zip in the HWOTA8 / repack folder. (I used STF-L09C432B120)
2. Run the bat file "repack" to repackage the zip files. This will prepare our firmware
I had a problem with this and had to update the file META-INF\com\google\android\update-binary by hand.
3. Create the folder "HWOTA8" on the SD card. (Without quotes)
4. Place the archive hwota8_update.zip, STF_RECOVERY8_NoCheck.IMG (from the HWOTA8 folder) and the three update archives (update.zip, update_data_public.zip and update_all_hw.zip (from the repack folder after repackaging)) to the "HWOTA8" folder on the sd card.
5. Boot into the TWRP
6. Install the hwota8_update.zip file which lies in the HWOTA8 folder on the sd card. The phone will reboot into the recovery mode and install the update automatically.
7. After the rollback, boot into recovery and make a reset
This was the first time, that I was able use the original recovery without problems.
I think I will try to do a rebrand at the weekend.