Hi there,
I bought ZTE U819 and I was trying to replace the Chinese recovery, but I chose wrong recovery version by mistake, so:
- I Can´t access to my device recovery (Up Volume + power).When I try to enter, the device always restart
- I Can´t access to download mode (It would be because the bootloader was deleted? mobileuncle tools says (when I try to reboot into bootloader mode) "MTK android have not bootloader mode")
- The device doesn´t recognize the external SD and internal storage either but if I search in the system folder "data", I can see all the apps I´ve installed with iAPK.exe)
- I only can access to system folder through root explorer
- It´s rooted
The only way to install apk is with iAPK.exe
* I tried to edit vold.fstab but didn´t work.
* I tried to install the chinese original recovery from adb but I couldn´t, because when I write down fastboot don´t find any device and always says "waiting for devices" (I have installed all zte drivers at least I think so...)
* I tried to copy the correct recovery to "data" system folder through android commander, and I got, then I copied the recovery in "data" system folder and I tried to flash with terminal emulator, but it didn´t work
* I tried to flash other ROMs (I tried to install 6) which I copied to "data" system folder with Flash Gordon APK but it always says "Is not a valid flashable ZIP"
What can I do to sort it out?
Could I replace any folder from the original .ZIP ROM, I´ve installed in my device, to the system folder through android commander?
If it´s necessary, I can upload all the system folders from the device and anyone could check them and find the problem.
Thank you ever so much!!
Any advice?
Nobody can help me?
bebito0077 said:
Nobody can help me?
Click to expand...
Click to collapse
I've the same problem, what is the solution?
I am bit late.. But why don't you flash stock ROM via SP Flash Tools, and flash correct recovery once again?
(Format everything except bootloader)
Related
Hello
here i am posting here because i cant post on Miscellaneous Android Development , how ever i think i post there before while working on B5512
I Just got new G700 it came with B115 middle east channel , phone is good but as a start is there is a update i must ask my self is root ready , and CWM for sure so i start the digging
@chamaruco thank you for your great thread which saved and helped many people
now i got a file and i think you were looking for it ""G700-U10_V100R001C00B124CUSTC432D001_Firmware_Portugal_Channel-Others_4.2.1_EMUI 1.8_05021LMW.zip"" it contain usb upgrade and sd upgrade with drv and flash tool
i notice EMUI 1.8 not 1.6 which i saw for example a permission manager with it on P6 is that here in that rom too ?
is that rom improved than mine b115 phone is good for first look but
(in B115)
1-camera quality is strange i dont mean bad but it look very strange it is like very poor on quality
2-in call volume is too low in my opinion all " in test mode"
Question now did any one get that update "EMUI 1.8 B124" can tell is there is any improvements ?!
Question am i able to flash CWM image directly with flash tool to save some annoying procedures ?!
a member here provide flasher and cwm.img and orginal recovery.img
i did not work with the phone yet need to shift data from old phone remove ext2 part and prepare for change , and feeling lost here
want to strike it all once
i will upload "EMUI 1.8 B124" soon as it came from a private server
any suggestions are welcome
When you install 1.8 you will notice there is only a tap error from uploader..it is a 1.6 emui. That's all.
Hello
some info to add
incase of softbrick the phone and unable to flash using spflash tool and receive " not allowed , forbidden "
solution
inside the usb upgrade >> flash "Rework-Secro" using scatter in same folder then you will be able to use download mode again
how to install this firmware i.e. B124 on G700-10
chamaruco said:
When you install 1.8 you will notice there is only a tap error from uploader..it is a 1.6 emui. That's all.
Click to expand...
Click to collapse
chamaruco; Thanks for the best of the best user guides you have been making for all of us, but what i want to know is to be able to install the B124 into my phone i.e. G700-10, i have rooted my phone using farmaroot, made a back up of my factory shipped OS and make all my data backup safe through Hisuit, have downloaded the firmware B124 Purtogal version, extracted the zip, (it is now carrying META-INF, boot.img, cust.img, logo.bin, sdload.log, system.img) i have made a folder in my SD card named dload and copied the files in it, uninstalled mobileuncle, reinstalled new mobileuncletool, copied my backuped recovery.img into my SDcard and somehow installed the recovery in to my mobile,
now please show me the way forward, what i need to do and how, please step by step if you kindly can. please.
YOU ARE THE BEST CHAMARUCO
talvigi said:
chamaruco; Thanks for the best of the best user guides you have been making for all of us, but what i want to know is to be able to install the B124 into my phone i.e. G700-10, i have rooted my phone using farmaroot, made a back up of my factory shipped OS and make all my data backup safe through Hisuit, have downloaded the firmware B124 Purtogal version, extracted the zip, (it is now carrying META-INF, boot.img, cust.img, logo.bin, sdload.log, system.img) i have made a folder in my SD card named dload and copied the files in it, uninstalled mobileuncle, reinstalled new mobileuncletool, copied my backuped recovery.img into my SDcard and somehow installed the recovery in to my mobile,
now please show me the way forward, what i need to do and how, please step by step if you kindly can. please.
YOU ARE THE BEST CHAMARUCO
Click to expand...
Click to collapse
Dload inside put update.app file, restart in updatemode
chamaruco said:
Dload inside put update.app file, restart in updatemode
Click to expand...
Click to collapse
But my mobile does not boot into CWM recovery mode as i have seen in my previous Qmobile A8 it always restarts in the defualt recovery mode which only give options to "1. reboot, 2. update from SDcard, 3. update from cashe, 4. wipe/delete user data and wipe/delete cache and in the last there is a calibarate TP, AND OFF COURSE THESE ALL ARE THE ANDROID BUILTIN RECOVERY STEPS NOT OF THE CWM
And off course there is not any file or folder named update.app in the downloaded .zip/extracted file. "as i have mentioned above the folder contains a folder named META-INF and three img files named as boot cust and system while a .bin file named logo too.
THANKS FOR YOUR TIME AND HELP.
foffa said:
Hello
some info to add
incase of softbrick the phone and unable to flash using spflash tool and receive " not allowed , forbidden "
solution
inside the usb upgrade >> flash "Rework-Secro" using scatter in same folder then you will be able to use download mode again
Click to expand...
Click to collapse
So after I select the Reworked scatter file there is only the sec_ro partition checked to flash. So after flashing it do I now select the previous scatter file and then flash everything (including preloader)?
Hi guys, Anyone knows about custom rom or custom recovery for this device?
Custom recovery is easy with the right tools!
marcosek said:
Hi guys, Anyone knows about custom rom or custom recovery for this device?
Click to expand...
Click to collapse
You can make your own ClockWorkMod custom recovery for ANY phone as follows:
WHAT YOU NEED
* Your phone with USB Debugging enabled
* Root access (in other words, your phone must be rooted)
* Busybox installed on your phone
* MTK Droid Tools
* Your computer
HOW TO DO IT:
1. Down load MTK Droid Tools and install on your desktop (do people still have those)
2. Install the Flashify app on your phone (from the Play Store)
3. Open Flashify on your phone
4. Select the Backup/Restore option
5. Back up the current kernel to your SD card (name it it stock_boot.img)
6. Back up the current recovery to your SD card (name it it stock_recovery.img) & close the Flashify app
7. Copy the two files from your SD card (it's saved under Android>data>com.cgollner.flashify>files>flashify-backup) to your desktop NOW YOU HAVE BACKUPS OF YOUR STOCK BOOT AND RECOVERY IMAGES IN CASE YOU EVER NEED THEM IN FUTURE
8. Run your MTK Droid Tools as Administrator and connect your phone to the desktop via USB (you'll see details about your phone in Phone Information ... you can ignore this but it does confirm that MTK Droid Tools recognizes your phone)
9. Now select the tab called "root, backup, recovery"
10. Click on the "Recovery and Boot" button
11. MTK is going to ask you where is the BOOT image for your phone...just select the BOOT image from the folder to which you copied the BOOT image on your laptop
12. MTK is now going to create a CWM custom recovery for your phone. It stores this in its subfolder called "recovery"
13. Now just go to this recovery subfolder. You will see TWO files. Now you rename the one that has "_recovery_" in the name to cwm_recovery.img. DO NOT MAKE THE BONEHEADED MISTAKE of using the file that has "_BOOT_PATCHED_" in the name!
14. Copy the newly renamed cwm_recovery.img to your SD card on the phone
15. Close the MTK Droid Tools program...it's work is done
16. Reopen the Flashify app
17. Select the Flash option and choose the RECOVERY IMAGE from the list of options. DO NOT...I REPEAT...DO NOT SELECT THE boot image OPTION. YOU WILL SURELY BRICK YOUR PHONE AND YOU WILL NEED TO FLASH A SYSTEM BACK TO THE PHONE. Since you have no custom recovery yet, you will be in a very difficult spot! DO NOT DO NOT DO NOT flash anything to the boot partition!!!!
18. Now that you have selected RECOVERY IMAGE, you can now choose the cwm_recovery.img and let flashify do its thing.
19. Once Flashify is done flashing, it will give you the option to REBOOT...do that
20. Behold your new CWM custom recovery
A couple important notes:
* I'm not responsible if you do something boneheaded like flashing the cwm_recovery.img to your boot partition and muck up your phone. I've already warned you repeatedly NOT to do that. It's an amateur mistake (that I made once...LOL!) DO NOT MAKE THIS MISTAKE!
* You did not really need the stock_recovery.img file for anything. BUT I MADE YOU BACK IT UP JUST IN CASE (you can always flash your stock recovery back to the phone). SAVE YOUR STOCK RECOVER AND BOOT IMAGES.
* USE YOUR NEW CWM RECOVERY AND IMMEDIATELY BACKUP YOUR ENTIRE PHONE TO YOUR SD CARD AND PLACE A COPY SOMEWHERE ON YOUR DESKTOP! Now you have two copies. If you ever want to return your phone to stock, just restore your backup and reflash the stock recovery. Then UNROOT your phone. Now, you're completely stock.
* While you're at it, use MTK Droid Tools again and select the SCATTER FROM FILE (and save the map somewhere convenient).
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!
I rooted my phone, and then i was trying to flash a Marshmallow Rom. For this, i wiped my system, boot, dalvik cache, internal memory. I forgot to take a nandroid backup. For some reasons, there was some error in flashing that zip file, so i tried to reboot my phone normally and it failed. When i reboot my phone, the company logo appears and it remain sticked there. For now, i could only access the recovery and fastboot. Please HELP me..... Thank you.....
You got exactly same problem with me but i have model: Honor7 Premium (PLK-L01)
Hi,
what did you expect? If you wipe de system partition then obviously the operating system is gone.
What you need to do is to download the full stock rom of your phone somewhere on the internet (needrom.com for instance if available).
You need to take the closest version of your old system and also the same technical name (PLK-UL00).
For instant if you were already on Android 6.0, you can no longer use a stock rom of Android 5.x.
When you have that full stock rom on your computer, you need to use multi-tools and use the unbrick option. Meaning you will be asked to extract the most important img files from the stock rom and to put them into a specified folder. The tool will then restore that rom on the partition file.
Kind reg,
I had android lollipop 5.0.2. Is it possible that i install the backup file of any other person's honor 7 PLK-UL00 running same android?
Hi,
please have a look there and use the stock rom that fits with your model and version.
https://yadi.sk/d/ZD8hXFjenRFHf
Kr,
how do i flash an UPDATE. APP file?
Create folder called dload on your SDCard and copy Update.app file to your SDCard inside that "dload" folder.
Then shutdown your device and use 3-Button method(Vol- & Vol+ & Power button) to boot that to recovery, that should start installing "recovery" file what is that Update.app inside dload folder.
Sent from my PLK-L01 using XDA-Developers mobile app
i don't know but the 3-button method is not working. When i do so, it boots to the recovery and nothing happens. Anyways, i have copied the dload folder with update.app file to the sdcard.
Use Multi-Tools available in the forum. There is a little app where you will be able to extract all required files from the file update.app.
Then in multi-tools use unbrick option and it will install the stock rom correctly. ++
http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Thank you!!!!! Sebastien_be and everyone to help me... It worked very well.. Thank u guys so much for the help...
1. My Redmi 5 Plus/Redmi Note 5 India is rooted, using TWRP and Magisk
2. I would like to know if there is a way that recent updates under downloaded_ROM can be flashed using a third party application such as Flashify?
3. I have come to this decision because when I tried to reboot device for installing recently updates, my device enters the TWRP recovery only find nothing in there, which is annoying. Root cause for this mess is that Xiaomi's fastboot rom downloads page is download, which would usually be my go to method after all. Using Mi Flash Tool, and then a few command types re-root the recently updated mobile phone.
Please guide me!
If I understood well if twrp it´s not recognicing (not really, only it can´t access) your data partition you need to format data at first time after to unlock and install a custom recovery in order that twrp can access to your storage directory.
Flashify just is capable to install boot and recovery images. Maybe you meant FlashFire, then to install it tap on + button and a menu will display with some options like Flash ZIP or OTA.
SubwayChamp said:
If I understood well if twrp it´s not recognicing (not really, only it can´t access) your data partition you need to format data at first time after to unlock and install a custom recovery in order that twrp can access to your storage directory.
Flashify just is capable to install boot and recovery images. Maybe you meant FlashFire, then to install it tap on + button and a menu will display with some options like Flash ZIP or OTA.
Click to expand...
Click to collapse
you're right, brother. I meant FlashFire, when I typed Flashfire. My bad.
I have the OTA downloaded from the official website, since the file I had in the downloaded ROM folder always returned an error as corrupt file when tried to open using Winrar. So I had to go the official site and get the same downloaded to see the contents inside.
But now, having copied the file to the downloaded ROM folder on my phone, I do not see any option as how I can choose the file to get installed. I mean there is no file explorer option given to me, rather Google Drive option. Perhaps I have to have the file uploaded once again on to my Google Drive on my device?
sengottuvel said:
you're right, brother. I meant FlashFire, when I typed Flashfire. My bad.
I have the OTA downloaded from the official website, since the file I had in the downloaded ROM folder always returned an error as corrupt file when tried to open using Winrar. So I had to go the official site and get the same downloaded to see the contents inside.
But now, having copied the file to the downloaded ROM folder on my phone, I do not see any option as how I can choose the file to get installed. I mean there is no file explorer option given to me, rather Google Drive option. Perhaps I have to have the file uploaded once again on to my Google Drive on my device?
Click to expand...
Click to collapse
Download again the file from the same site, maybe downloaded to your Google Drive is corrupted and check that the extension didn´t change from .zip to .rar or FlashFire won´t recognice it. Winrar have to be capable to open it otherway the file is corrupted.
When you are sure that is the correct file If you had a stock recovery then you can install it through update option in settings/about device/updates from miui menu