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.
Related
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!
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Reserved
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
cland216 said:
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
Click to expand...
Click to collapse
Hell yeah. Glad I could help somebody! I've been wanting to give back to the wonderful XDA community for a while as a long time lurker. Also, I'm hoping to get a newer version of the stock rom and a stock recovery.img so you can go back to 100% factory stock for an OTA. I'm pretty proud of myself (being noobish) figuring this out.
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
klaudio_tv said:
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
Click to expand...
Click to collapse
Are you referring to "extracting" the recovery img? You only need to do it if you're running the stock recovery.
If so, I think I have screwed the command. Make sure you're in adb shell (in recovery on the watch) and then type "cat /proc/mtd" (with the space in front of cat) without the quotes in order to locate the recovery partition.
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
Hopefully this works
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
klaudio_tv said:
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
Click to expand...
Click to collapse
Since the OP helped me, here's my chance to give back..
By no means do I know what hell I'm doing, but I know enough to be dangerous. If you're ready to live dangerously, follow these steps (which worked for me):
1. Go into TWRP on the watch and connect it usb to your computer. Using TWRP file manager, copy the update.zip from CACHE to sdcard\Download.
2. On the computer, browse to Zenwatch internal memory Downloads folder and copy the update.zip file to your computer.
3. Unzip the file on your computer using 7zip.
4. Navigate to \META-INF\com\google\android\ and look for updater-script.
5. Edit updater-script in Notepad++.
6. Delete the lines starting with getprop. This turned out to be lines 2 thru 5.
7. Delete the lines starting with apply_patch_check. This turned out to be lines 10 thru 176
8. Save changes to updater-script then in Windows Explorer highlight all of the files and folders that you unzipped, right-click them and click on 7zip --> Add to update.zip
9. Copy the new update.zip to the Zenwatch internal memory, Downloads folder, overwriting the original update.zip
10. Flash the update.zip file with TWRP.
11. Reboot TWRP to Bootloader.
12. On your computer, goto adb folder where you have fastboot files, and using command prompt type:
fastboot erase cache
fastboot erase misc
fastboot reboot
These steps worked as I was stuck on the June 1, 2016 Android security patch on my Wren Zenwatch. These steps helped me get to the September 1, 2016 security patch.
I managed to update my watch to the September 1 security patch using Cland216's method. But I am unable to update further using the method above. Does anyone have any info on how to update further? Or has any zip files to flash?
If we could get someone to upload the watches stock recovery that would solve all issues.....Why has noone done this for this model yet?
Sent from my OnePlus X using XDA Labs
I'm unable to create a backup file
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
TWRP :
Could not mount /data
When I try to mount /data , I unable to /data
HOLY ****
Dude.. Let me just say...
YOU ARE THE ****ING ABSOLUTE BEST.
I am now going to make a backup, and save it to my computer, google drive, dropbox, icloud, and every other ****in place I can to make sure this never happens again. Thank you!!!!
Nicholas6706 said:
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Click to expand...
Click to collapse
I spoke just a bit too soon, now it is hanging on that animation with the 4 dots. Any suggestions?
NEVERMIND, I AM UP AND RUNNING!! WOOHOOOO
I tried to root my watch a while back and kind of gave up. Since then, I have installed both the stock recovery and system image found in this thread:
https://forum.xda-developers.com/zenwatch-2/general/m6e69n-twrp-backup-stock-boot-firmware-t3484961
Now, I keep getting the update to M6E69X and it goes through the normal process of updating, but then a picture of an Android with an exclamation point comes up. I'm almost positive that its similar to the issues of newer versions of Android on phones requiring complete stock systems to update. The only problem is, I have tried reflashing the backup in the link above about four times now and it still won't work.
Any help will be appreciated at all and I'm sorry if this has been answered before and I'm just blind.
About 4 down from your post, https://forum.xda-developers.com/zenwatch-2/help/m6e69x-stock-rom-t3564626
At the bottom of that thread is a zipped up TWRP backup. Get TWRP temporarily running on the watch and restore it from there.
Here are the brief steps I did.
1. Get ADB Minimal and Fastboot - plug your watch into the computer using the cord. Enable ADB debugging on the watch.
2. Get twrp-v3.0.0-0.jk-v3.recovery.img for the watch
3. Fastboot oem unlock (erases your /data partition)
4. fastboot boot twrp-v3.0.0-0.jk-v3.recovery.img
5. Make an initial backup of the watch. You'll need the file structure created.
5. TWRP should let you copy the files to/from the watch
6. Create a new folder and copy the files from the zip to a folder under the serial number folder below TWRP - I have folder called 2017-03-14--11-51-50_M6E69X
7. Restore that copied TWRP backup
Hope that helps.
Hello everyone
I hope somebody can help me. I have a Huawei y6 scc-u21 that I need to fix. I have downloaded a firmware flash file to reflash the phone however, after doing so, I found that the gapps are not installed. I tried to download and install every update but still I did not have gapps installed.
Also, I noticed that after flashing and everytime I do a factory reset, the phone would not prompt me to a setup process and just automatically goes to the normal interface. Some settings are missing too.
Please help. Without GAPPS this phone is basically useless. Doesn't even get a signal even though a SIM card is inserted.
Thanks.
I had the same problem.. here is what i do to solve it:
1- download u21 cm2 backup file from here:
http://www.mobilekse.com/2018/09/huawei-y6-scc-u2131-all-file-firmware.html?m=1
2. Extract it with 7zip.
3 download an sd card update "update.app".
4. install the update with sd card.
5- extract the file with "huawei update extractor" and get "BOOT.img" , "ABOOT.img" and "CUST.img" rename them to lowercase and put them to the folder of the first firmware of step 1/
6- open qfil, select flat buit, select the programmer path from the firmware folder then select from the top: tools then partition manager.
7- select boot.img partition and with a right click select manage partition.
8- choose the boot.img extracted and replaced.
9- do the same for aboot.img and cust.img
10- the phone will exit this dump mode and you will find playstore, keyboard, notfications..
Ask me if you found anything not clear
this is a guide for some user running stock Realme UI 2 on rooted device. while stock recovery wont work after unlocking bootloader and magisk installed (UPDATE: apparently stock recovery are working but you have to wait around 30minutes in order to boot into it). the only option for us is using custom recovery. but custom recovery wont recognize the updates because it's unusual format and its unusual location. Be careful!! I'm not responsible for any damage you may encounter doing this guide. I will try to help as far as I could do
(this guide are documentation from rui2.0 c.09 to c.15 update. where rui1.0 to rui2.0 upgrade im using stock recovery )
first of all, we need to download updates from ota server. simply enter Settings app, scroll down and select Software update. wait untill finished, you'll be prompted to install when it's done. but don't have to do that, it only reboot to recovery doing nothing.
now preparing the updates.
the downloaded files are located inside
Code:
/data/ota_package/OTA/.otaPackage
there are 6 files (may vary) and all of them are flashable zips except system_vendor that needs slight modification. copy or move those files to internal or external storage (i personally put those files on /sdcard/updates/). then add .zip extension by renaming (put ".zip" in the end of file name).
modifying system_vendor.zip
extract system_vendor into separate folder. after that, navigate to META-INF/com/google/android/ now edit updater-script replace RMX2151L1 (or similar) with RMX2151 to avoid installation errors. on TWRP, this phone is only recognized as RMX2151 regardless it's actual phone model ( it needs confirmation from other realme 7 users ).
now back to system_vendor folder and replace vbmeta.img file with vbmeta from attachment. after doing all steps simply repack all files and folder into zip with normal compression parameter. (you don't have to replace vbmeta file, but you have to flash modified vbmeta after that to avoid bootloop)
all files are ready to flash using TWRP (or your own preferred custom recovery). flashing this zip might replace bootloader with stock so flashing Magisk are preferred or you'll lose root access.
the intention of making this thread are opening discussion about realme updates. maybe someone out there could make all those steps simpler and easy enough