I've read LOTS of the threads here and maybe it's just beyond my brain to wrap around but I've also dl'd linked files in the hopes of fixing the one broken tablet.
Both tablets are Sony S and 111US. They have NEVER been rooted as I'm unfamiliar with the practice; though I can understand now why it's a nice thing to do from some of these posts/solutions.
I am borrowing this working tablet from a friend in the hopes I could find the answer by copying them via a File Explorer on the working tablet.. I can't send the broken one in to Sony as it was a gift and I don't have the receipt / proof of purchase; which the representative stressed that I needed in order for them to fix it.
Sometimes it's just stuck at the Sony Logo and one time when I tried to do a recovery from a file via SD card I got from condi or stifilz's 4shared.. well it was stuck at the shimmering boot animation; naturally I was SO excited but then it died down when I saw it was looped at that.
So my prime question is.. In putting a File Explorer on the WORKING tablet [not rooted and not updated, fresh from the box pretty much]: Is there a way to find the necessary files I need to fix the broken one?
Thanks!
kitka82 said:
I've read LOTS of the threads here and maybe it's just beyond my brain to wrap around but I've also dl'd linked files in the hopes of fixing the one broken tablet.
Both tablets are Sony S and 111US. They have NEVER been rooted as I'm unfamiliar with the practice; though I can understand now why it's a nice thing to do from some of these posts/solutions.
I am borrowing this working tablet from a friend in the hopes I could find the answer by copying them via a File Explorer on the working tablet.. I can't send the broken one in to Sony as it was a gift and I don't have the receipt / proof of purchase; which the representative stressed that I needed in order for them to fix it.
Sometimes it's just stuck at the Sony Logo and one time when I tried to do a recovery from a file via SD card I got from condi or stifilz's 4shared.. well it was stuck at the shimmering boot animation; naturally I was SO excited but then it died down when I saw it was looped at that.
So my prime question is.. In putting a File Explorer on the WORKING tablet [not rooted and not updated, fresh from the box pretty much]: Is there a way to find the necessary files I need to fix the broken one?
Thanks!
Click to expand...
Click to collapse
Best thing to do would be try to flash the lowest update you can such as signed-nbx03_001-ota-11000.001.zip or 0035 or 0042. These are all HoneyComb (oldskewl android). Then use ADB pull /tmp/recovery.log and post the file here, then we can see what is happening.
any questions see my FAQ on how to flash etc
Stifilz
stifilz said:
Best thing to do would be try to flash the lowest update you can such as signed-nbx03_001-ota-11000.001.zip or 0035 or 0042. These are all HoneyComb (oldskewl android). Then use ADB pull /tmp/recovery.log and post the file here, then we can see what is happening.
any questions see my FAQ on how to flash etc
Stifilz
Click to expand...
Click to collapse
I was afraid of that :/ Tried to download the files you directed me [I have bookmarked your 4shared]. They download fine however.. when I try to put them onto an SD card I get a popup to "Please insert the last disk of the Mult-Volume set and click OK to continue"
Trying to extract [for the heck of it] on computer.. I get that "The compressed (zipped) folder is empty."
Maybe the storms overhead here are making my net connection too funny to download anything atm.. I am not really sure. [Though I'm questioning why it's taking 30mins+ to download each file]
Despite those errors.. I pop the SD card into the tablet and not too surprised, the file doesn't show up TO load.
This happened with: signed-nbx03_001-ota-11000.zip and signed-nbx03_001-ota-0035.001.zip
I am still working on the others with the hope that I'll find success in ONE of them.
kitka82 said:
was afraid of that :/ Tried to download the files you directed me [I have bookmarked your 4shared]. They download fine however.. when I try to put them onto an SD card I get a popup to "Please insert the last disk of the Mult-Volume set and click OK to continue"
Trying to extract [for the heck of it] on computer.. I get that "The compressed (zipped) folder is empty."
Maybe the storms overhead here are making my net connection too funny to download anything atm.. I am not really sure. [Though I'm questioning why it's taking 30mins+ to download each file]
Despite those errors.. I pop the SD card into the tablet and not too surprised, the file doesn't show up TO load.
This happened with: signed-nbx03_001-ota-11000.zip and signed-nbx03_001-ota-0035.001.zip
I am still working on the others with the hope that I'll find success in ONE of them.
Click to expand...
Click to collapse
Use Fat32 sd I have same trouble with my exfat sd card
rooted lighting wildfire on unoffical j.b from benni
and sony XTS rooted stock j.b thanks djrbliss
kitka82 said:
I was afraid of that :/ Tried to download the files you directed me [I have bookmarked your 4shared]. They download fine however.. when I try to put them onto an SD card I get a popup to "Please insert the last disk of the Mult-Volume set and click OK to continue"
Trying to extract [for the heck of it] on computer.. I get that "The compressed (zipped) folder is empty."
Maybe the storms overhead here are making my net connection too funny to download anything atm.. I am not really sure. [Though I'm questioning why it's taking 30mins+ to download each file]
Despite those errors.. I pop the SD card into the tablet and not too surprised, the file doesn't show up TO load.
This happened with: signed-nbx03_001-ota-11000.zip and signed-nbx03_001-ota-0035.001.zip
I am still working on the others with the hope that I'll find success in ONE of them.
Click to expand...
Click to collapse
Yeh what dex9mm said. Try to format the disk and then put it onto sd card. Also the files are encrypted so you can't extract them. Are you copying straight to sdcard (laptop) or using a reader?
stifilz said:
Yeh what dex9mm said. Try to format the disk and then put it onto sd card. Also the files are encrypted so you can't extract them. Are you copying straight to sdcard (laptop) or using a reader?
Click to expand...
Click to collapse
Hmm.. didn't think of formating them first but okay shall do that.
When I click "download" it auto-downloads to my folder on Computer. From there I then "copy to" the card. Thanks guys!
UPDATE: Okay.. so I FINALLY got the tablet to see the ota 1100, 0035 and 0042 and got, to my unending frustration, the repetitive error:
"Erohibit update as a result of checking version or base sku
Installation aborted"
What's that mean exactly? and is there a way to fix that? Not sure if I need to find a decrypted zip and edit something in it now.. :/
Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!
it all started when internet could not open a pdf file (cannot download because sd card was unmounted )
also the camera function didn't work anymore, when starting the camera software, i got an error saying there was no memory card.
i checked under settings for the storage and i see
-internal 1GB system storage and see it has limited data free
-internal 7GB SD card (i think shared drive with system). android is checking this disk for available capacity and then it disappears. i get SD card is unmounted
-external 16GB micro SD card that is mounted as SD-ext.
rebooting didn't help, then I performed a factory reset within the android OS: all settings gone, still no internal SD
then i went into recovery and performed a data reset, again everything working but still no SD card.
i have googled for yarvik noble 10c rom and found a pdf from yarvik website explaining in detail how to do a firmware upgrade. on the website there is no rom available. also the forum.yarvik.com doesn't excist anymore. sending an email to yarvik asking for help didn't got me any answer.
I installed CWM. i performed a backup from the image to my sd-ext and then looked at the files.
system.ext4 is empty (recovery.ext4 and boot.ext4 are good).
i also found some other rom's from yarviks with almost same specs. i can extract the system.img file from the image, but don't know how ik get them back on the tablet.
can't get the tablet in pc download mode (power on and sound+ pushed in). i only can get in recovery mode.
i download like 100tools the last hour and can't get anything working (like ADB). i using a win7 machine and not linux (my linux laptop is not working anymore) and it gets very difficult.
is there some way to use cwm to use img files to extract? or some other tool that can work in recovery?
how can I put a complete image on my external SD and perform a system restore? i used the original update tools but they don't see the device connected.
ADB has no connection while the tablet is waiting for adb commands. my computer lists no devices (win7, winXP and ubuntu 14.04.1 LTS).
contacted yarvik, no answer, contacted sweex, also ne reply. found on the internet that yarvik and sweex don't exist anymore. sweex has been bought by nedis, but yarvik not. gonna go to store today and see what they say. still have warranty but if no company can repair it anymore...
fcapri said:
I installed CWM. i performed a backup from the image to my sd-ext and then looked at the files.
system.ext4 is empty (recovery.ext4 and boot.ext4 are good).
i also found some other rom's from yarviks with almost same specs. i can extract the system.img file from the image, but don't know how ik get them back on the tablet.
can't get the tablet in pc download mode (power on and sound+ pushed in). i only can get in recovery mode.
i download like 100tools the last hour and can't get anything working (like ADB). i using a win7 machine and not linux (my linux laptop is not working anymore) and it gets very difficult.
is there some way to use cwm to use img files to extract? or some other tool that can work in recovery?
how can I put a complete image on my external SD and perform a system restore? i used the original update tools but they don't see the device connected.
ADB has no connection while the tablet is waiting for adb commands. my computer lists no devices (win7, winXP and ubuntu 14.04.1 LTS).
contacted yarvik, no answer, contacted sweex, also ne reply. found on the internet that yarvik and sweex don't exist anymore. sweex has been bought by nedis, but yarvik not. gonna go to store today and see what they say. still have warranty but if no company can repair it anymore...
Click to expand...
Click to collapse
Yarvik as filed for bankruptcy so it will never support their devices ever again. They even taken down the page where the firmwares are located.
I have the same model bricked since june and never found any software that worked. If someone could supply an original rom from yarvik it would be great.
Regards
uha666 said:
Yarvik as filed for bankruptcy so it will never support their devices ever again. They even taken down the page where the firmwares are located.
I have the same model bricked since june and never found any software that worked. If someone could supply an original rom from yarvik it would be great.
Regards
Click to expand...
Click to collapse
i have printed some newspaper artikels about sweex and yarvik (sweex being bought bij nedis and yarvik is gone). went to the store today where i bought it, and they wanted to send it back to yarvik. i showed them the artikels and told them yarvik don't exist anymore.
the offered me a refund and i bought an asus 10" tablet . problem solved and since one hour my samsung android phone stopped working
Hi folks, first up, apologies for starting a new thread, but i am completely lost and couldn't find any solution online and wasn't sure which thread to post this in. So here is my situation
So, i upgraded my mediapad x1 to 7D-501u a week ago, and it was working well. While on it, i rooted it and did the following tweaks
1. to install google apps i did the tweak at the following link http://forum.xda-developers.com/showthread.php?t=2757537 (which is 1. Go to the following folder 2. / cust / channel / charm_china_u / xml / 3. You will find the file UNSTALL_APK.XML 4. Rename it to : UNSTALL_APK.XML.OLD)
2. I changed the DPI to 400 by changing build.prop
Then, i wanted to give the phone to my sister and did a full factory reset (without undoing the changes above). Now, none of the keyboards work after the reboot, (Huwaei keyboard is all messed up resolution wise, if i choose any of the other keyboards they FC). I tried reinstalling the rom itself, but it give me an error saying unable to mount update.app
Any ideas on how to proceed? I am stuck right now.
Install https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en
this keyboard usually works on all dpi settings.
ashish1607 said:
Install https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en
this keyboard usually works on all dpi settings.
Click to expand...
Click to collapse
Hi Ashish, thanks for that, but currently i am unable to type anything on the phone that has been factory reset, so i havent been able to setup my google id, havent been able to download anything in the play store etc. I was just wondering if there was a way to overcome that problem of the update.app not being mounted.
When i try to update, it gives me a message saying update file found, but cannot mount update.app
Hi,
Try to connect your x1 to your PC with Hisuite software installed on your PC. If your x1 can connect with Hisuite, you can then reflash your firmware again (I hope).
boysha8 said:
Hi Ashish, thanks for that, but currently i am unable to type anything on the phone that has been factory reset, so i havent been able to setup my google id, havent been able to download anything in the play store etc. I was just wondering if there was a way to overcome that problem of the update.app not being mounted.
When i try to update, it gives me a message saying update file found, but cannot mount update.app
Click to expand...
Click to collapse
Are you trying to reflash the firmware from within the OS? If yes, you are getting the error because you have rooted.
You will need to put update.app into a folder named 'dload' then put the folder at the root directory of your SD card, switch off the phone and force flash.
You can force flash by holding both the vol up and down, and the power on buttons concurrently, when you see the screen lit up, do not release the buttons yet, only let go of them when flashing starts.
At the end of the flash, you will / may be asked to removed the SD card (if you were not asked, pull the card out when the phone reboots, else it will attempt to flash again).
bthoven said:
Hi,
Try to connect your x1 to your PC with Hisuite software installed on your PC. If your x1 can connect with Hisuite, you can then reflash your firmware again (I hope).
Click to expand...
Click to collapse
Thanks a lot. I managed to install a new keyboard and adjust the resolution and stuff. But i am now not able to upgrade or install a different rom version. Once it enters recovery mode i keep getting this same message below.
ERROR:update_package_exist, /sdcard/dload/update.app not mounted
i tried updating using the sd card, i tried using the hisuite software etc. I undid the unstall_apk xml thing, and changed the resolution back, but still no luck. Any pointers will help
boysha8 said:
Thanks a lot. I managed to install a new keyboard and adjust the resolution and stuff. But i am now not able to upgrade or install a different rom version. Once it enters recovery mode i keep getting this same message below.
ERROR:update_package_exist, /sdcard/dload/update.app not mounted
i tried updating using the sd card, i tried using the hisuite software etc. I undid the unstall_apk xml thing, and changed the resolution back, but still no luck. Any pointers will help
Click to expand...
Click to collapse
Please Format your SD card as NTFS.AT unzip your ROM from Huawei website.(B010 version recommaded).and gointo systemupdate and selcet local
Hello! First post here!
Just got a new STF-L09 on the amazon cyber Monday sale (had an iphone before) and in my excitement to start messing with it, I managed to brick it.
I was following this guide: https://forum.xda-developers.com/honor-9/development/beta-twrp-3-1-1-0-t3654355 and did a full format through TWRP to try and get rid of the encryption in order to root it. Now my device is in a bootloop. I've been looking through older posts here on XDA, boycracked and a few other places but there seems to be quite a bit of contradictory information and I don't want to make anything worse.
What I have:
- An unlocked bootloader
- Working TWRP 3.1.1
- ADB and fastboot (over USB from my laptop running linux)
- A microSD card
- Ability to boot to force update process
What doesn't work:
- my TWRP backup (I didn't realize the one I tried to make failed/got deleted).
- the stock eRecovery tool. Even on stable wifi it cannot retrieve package information from server. I'm assuming this is because Huawei hasn't made the recovery firmware available over this channel for this model.
I'm now trying to do a force update using a stock ROM and my external SD, but I'm having trouble for two reasons:
1. I'm not exactly sure what my initial firmware was, so I'm not sure which ROM to pick.
2. I can't successfully transfer the contents of the update.zip I'm trying to use into a dload folder on the root of my sd. I'm assuming this is because the sd card is formatted to vfat and the UPDATE.APP file is larger than 4GB and therefore not supported on vfat.
Can anybody tell me:
A. How to find out what my initial firmware designation would have been? Phone was recently purchased for UK market, blue colour, 64GB internal memory. Came with EMUI 5.1. I have S/Ns and so on if that helps.
B. How to perform force update with microSD in my situation? Can I format the card to NTFS or another format that supports >4GB filesizes? Am I using the wrong ROM (This is the one I'm trying to use: http://androidhost.ru/v5 )? What files exactly should go into /dload/ at the root of the sd?
C. Is there another procedure I should try in my case? I am able to use fastboot, and I understand it would be possible to flash files onto the device using that, but I'm just getting started with Android and I'm not really sure about the functions of the various images/partitions (eg. data, cust, boot etc.). Is there any hope of the eRecovery tool coming online?
I know some of you have had some success coming from similar situations. I'd really appreciate any help you guys could give. Happy to throw some dosh to anyone who can help put me back in business!
Fixed my own problem 5 minutes later with help from this thread:
https://forum.xda-developers.com/honor-9/help/help-to-restore-l09-bootloop-t3651641
Wrote up my procedure there. But thanks anyways guys!
:victory: