Hello friends,
I was using a General Mobile etab4 tablet,
rooted,
bootloader locked,
not backed up, i tried but apps wont recognize the brand,
the stock rom is not available anywhere but I managed to find some custom ones.
This tablet is actually a given by government for educational purposes, and it has no download mode, I can only initiate recovery mode with volume up+power button combo, and there is no sd card in it.
Here is what happened. It was running with problems so I decided to flash a custom rom I find on this forum. First I tried flashing using adb sideload. I got an error message "Installation aborted" with no error codes after verification step but it does not state whether verification is failed or not. I don't know what actually failed. Then I tried to flash it using adb shell as root (the system image was in /sdcard directory). It freezed, I exit the shell using Ctrl+C command. Then whenever I try to start shell i got "error:closed" message. I see my device with adb devices with sideload, but it is not seen in fastboot devices.
When I try to open it, I guess it enters in a small boot loop (screen flickers multiple times with brand name on it) and after some time I got dead android with no command written.
I tried,
reflashing it again with Android AIO Flasher,
use fastboot to unlock bootlader (it says "waiting for device") although adb devices sees it,
re-installing the adb drivers after uninstalling them,
disassembling the device to see if I can detach memory to edit it and to see if disconnecting the battery helps,
I even used a simple jig to see if i can initiate download mode (know it works for specific devices but you know hope)
Apparently, I messed up the device but the hardware must be all fine. So I think there must be a way out. What can you suggest, I wish I have unlocked the bootloader. I can send the pictures of its motheboard it helps,
Thanks in advance.
Hi all, this is my last hope at the moment. Any input would be highly thanked.
I own an ASUS Padfone 2 (KOT49H.WW_Padfone-11.8.4.23-20141028), stock firmware, that I managed to get soft-bricked, as I read they call it.
Phone is unrooted, ran KitKat, and I really don't know much more about it, I'm not really an expert unfortunately... No custom ROM or any of those pro stuff.
Scenario:
Every single app crashed upon opening, performed a reboot, phone got stuck into infinite boot-loop, at the company logo in the beginning.
What can the phone do and what I've done so far (all of which have been found through internet):
I can enter into recovery mode.
Did a factory reset and wiped cache partition before the following.
I entered what the phone calls "CSC mode", that other sources call "fastboot mode".
Followed this guide http://forum.xda-developers.com/showthread.php?t=2256977 , installed drivers, entered into the proper directory on CMD, and typed "fastboot boot recovery.img", but CMD says "OKAY" and all, but gets stuck at "booting...", even after like 15 minutes.
Then, for whatever reason I saw on the internet, I tried the command "fastboot oem unlock" that also didn't finish anything either in CMD or (seemingly) on the phone.
Then, I tried following this guide in CSC mode (even though I don't have the invalid kernel error) http://www.modaco.com/forums/topic/365818-padfone-2-invalid-kernel/#comment-2191432 , but also didn't get any further than CMD stuck at "booting..." for forever.
I suspect it could be possible to do some of those booting magic, but I have no clue how it works and how my problem inside the problem could be solved...
Thank you so much in advance.
(Please beware that I don't understand what the words bootloader, fastboot, flash or ROM mean. I'm a mere mortal.)
Hi, I was running leedroid m9 rooted s-off with twrp and it was working great until I had some bizarre out of nowhere system app crashes earlier tonight (I guess yesterday by now). Commence boot loop. At first I was unable to access recovery and was just met with another shorter boot loop. I was eventually able to get into recovery through the bootloader menu but with a glaring fault. It gave me the prompt as if it was the first time booting into twrp, asking if I wanted to leave the partitions in read only mode. I thought "well kinda weird but ok". Then I try to restore my last post install image. It starts out with something about being unable to mount data or find the crypto header, and then it's nothing but "failed to mount x (invalid argument)". Same result for everything. Wipe, failed, adb sideload, failed, even manually attempting to mount in terminal failed (invalid argument). We even tried just completely opening up permissions (I know, very bad move for security but we were at our wits end). Unable to detect the phone via RUU or ADB in any state I can get it to boot to. I imagine something going on with encryption is to blame here? But I don't recall opting for or setting up any encryption?
Basically, is this phone beyond hope? Is there anything magical I can do through the bootloader (also not detected by adb)?
Also, looking in terminal in twrp, I'm still a root user? Don't know if that helps shed a light on this.
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.
In such cases, you cannot reach adb from the command line, so there seems to be no way to recover the watch. Fortunately, it has been discovered how fastboot can be entered without a running system.
2. Procedure
Step 1: Get into fastboot
This is the most difficult part. @kiralex1995 has developed a procedure that will lead reproducible to boot the watch into fastboot mode, but it may take many tries (one user reported that it took him 30 min of tries).
Follow this guide: https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829
When you are in fastboot and see the fastboot logo, you have mastered the most difficult part.
Step 2: Choose a ROM to flash on the watch
There are currently three possible ROMs to choose from:
a.) The English AmazFit firmware 1.3.0n
Download the following file on your PC: https://mega.nz/#!xIkC1IQZ!bLLSN9BMvbp7zhZHg2oQq6p4ud-EFyUYkatCGKgHeS8
b) The Chinese AmazFit firmware 1.2.5a
Download the following file on your PC: https://mega.nz/#!tNdggR4b!VXmExGqdNixrj8pVLqTkAi_munmjF5RidRJP9L-LAXE
c) An old Chinese AmazFit firmware 0.9.50:
Download the following file on your PC: https://mega.nz/#!wY9mEQoI!0ARB0MaK0byjttgrPmJJQX4ZFdIXgHOUquxqFhghg7U
Step 3: Download flash script from xda
Download the attached flash script from this post to your PC.
Step 4: Unpack the archive on your PC
Depending on you PC choose the right method to extract the files in the ROM archive and the flash script.
Step 4: Boot the watch into special recovery
Check that your fastboot drivers see that watch (which should still show the fastboot logo):
'fastboot devices'
You should see your device listed. Otherwise check your fastboot driver installation on your PC. (Note: On Linux you sometimes need to use "sudo fastboot ...".)
Then boot the modded recovery that is included in the archive you unpacked in step 2.
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
Step 5: Transfer the ROM files and the flash script onto the watch
First check that you are now able to connect to your watch via adb:
'adb devices'
You should see your watch listed. Otherwise check you "adb driver" installation. For Windows take care that you use Khoushs universal adb drivers.
Then push the files to the watch:
'adb push boot.img /data/media/0/
adb push system.img.gz /data/media/0/
adb push md5s.txt /data/media/0/
adb push flash_rom.sh /data/media/0/'
Step 6: Enter the shell on the watch and check your files
After you have successfully transferred the files to the watch, you then enter the shell on the watch:
'adb shell'
You should see only a "#", meaning you have full root access.
Now switch drirectory to the sdcard
'cd /data/media/0/
ls'
You should see your files on the "sdcard", including the ones that were pushed before
7. Start flashing the files
Run the flash sccript with the following command on the watch:
'sh flash_rom.sh'
If everything worked correctly, you should see something like:
Code:
Validating images
boot.img.gz: OK
system.img.gz: OK
Starting to flash now. DO NOT TURN OFF OR REMOVE THE USB CABLE! Press Enter to continue or CTRL-C to stop!
Flashing boot.img
2304+0 records in
2304+0 records out
9437184 bytes (9.0MB) copied, 2.075793 seconds, 4.3MB/s
Flashing system.img
210944+0 records in
210944+0 records out
864026624 bytes (824.0MB) copied, 107.981352 seconds, 7.6MB/s
Finished
If you see any error message during or after flashing, then DO NOT REBOOT the watch, but get some help or analyse yourself, what went wrong. You can still reflash.
8. OPTIONAL: Delete the dalvik-cache
You can erase the dalvik-cache on the watch with the following command:
'rm -rf /data/dalvik-cache'
This will make the system "re-optimize" all apps when it boots (successfully) the next time. This is optional, as you could always do that later again.
9. Reboot the watch
If everything is ok, then you can reboot the watch
'reboot'
Your watch should boot normally into the flashed system, you downloaded. CONGRATULATIONS, you unbricked your watch!
Thank you for this post.
Neuer_User said:
In case you bricked your watch, here is a tutorial how to unbrick the watch:
1. What is a "bricked" watch?
A bricked watch does no longer boot. It typically stops at the boot logo and waits forever. This can happen for example, if a flash of the system image failed and the boot image can no longer boot the system.....[/B]
Click to expand...
Click to collapse
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
First watch has just successfully been unbricked (1immortals watch) [emoji106] [emoji2]
kiralex1995 said:
I'm so happy that my post help people. Thanks to your job and thanks to your rom @Neuer_User .
I wonder if it would be possible to create a rom with all google services included ?
Click to expand...
Click to collapse
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Neuer_User said:
Yes, it would be possible. But you also need to look at connectivity. The watch checks does turn off wlan automatically.
Click to expand...
Click to collapse
Well i guess constant WiFi would dramatically reduce the running time? On the other hand it might just be turned on for short periods, don't know how Google does that.
1immortal said:
@Neuer_User, you're a GOD !!!
All bow @Neuer_User , he is the true ruler of Amazfit, conquer of the M200 SoC, bringer of root to the MIPS platform ! all hail the king !!!
Click to expand...
Click to collapse
Congratulations and thanks to Neuer_User.
hi, after this step the watch reboot and restart the loop on logo. why?
'fastboot boot Amazfit-mod-recovery.img'
You will see a "FAILED" message on your commandline. This is normal.
On the watch you should see the recovery triangle and the text "No command".
edit: after more test, i'm not able to go to recovery mode. For an errore, when i try another time to go to Fastboot mode, i push 2 times the button and i ERASE ALL the watch, now i have a device called JZ4785 USB Boot Device.
There's some way to save this watch?
Thanks.
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
1immortal said:
I think that you have entered some "Deep" flash mode - the JZ4785 is the SoC model, and you need to provide a driver for the flashing process.
please download this tool:
ftp://ftp.ingenic.com/DevSupport/Tools/USBBurner/cloner-1.2.0/cloner-1.2.0-windows_release.zip
you will need a 32 bit machine for running that.
it contains the drivers and the software for flashing. I hope that there's a way of creating a dump file of a working watch, and flashing it directly on yours.
Click to expand...
Click to collapse
This could indeed be the case. Noone of us ever entered that mode so far. It would be very good to understand, how you really got into that. It must have happened in the first step, where you were supposed to enter fastboot. Did you see the screen on the watch with the two options? There is a video in the link of @kiralex1995 post. Maybe you can comment, what exactly looked identical for you and where it exactly started to differ.
In case, you are really in that SOC flash mode, the Ingenic USBburner tool would indeed, probably, be the right tool to reflash the watch. As I mentioned, nobody here used that before. I have some experience with similar tools for the MTK platform. I believe that it should be possible to generate the necessary dump from a working watch, but this is all theory so far.
Where are you located?
well, nothing helped, there's no configs for the JZ4785, and there's no relevant information of partitions offset for flashing. we tried to flash both 1.2.5 and some generic ingenic image, with a lack of success as well
contacted ingenic for some clarification and some help, lets see where this lead to ...
Hello and thanks for tour support.
Also "launcher has stopped" i have to consider as a brick situation?
Palese led me know because i tried to update from chinese firmware but Now it doesn't work, i am able to start in fastboot mode
Thank you vero much fo and your advice
regarding the launcher errors, please try to unpair your watch and re-pair it again, it's a non-brick situation.
after i worte: fastboot boot Amazfit-mod-recovery.img . it says:
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
alon1211 said:
after i worte: fastboot boot Amazfit-mod-recovery.img . it says:
downloading 'boot.img'...
FAILED (command write failed (Unknown error))
finished. total time: 5.014s
Click to expand...
Click to collapse
Try a different USB cable. Bad cables are known to produce that error.
This is pretty awesome! I used this to convert my Chinese Amazfit watch to English ROM, and it seems to work OK.
However, there's a piece missing from the bundle -- the recovery image. There's an OTA available, and I pulled the update.zip file using the Fastboot trick so the OS didn't load and delete it - then booted the "mod recovery". Here's that update.zip (to 1.3.2b): https://mega.nz/#!nIBDhLrR!7nQlWsn-TF4bsMNBSaTOfimY-vo-Z2R3dSavrDp1wsA
The OTA didn't succeed -- when it went to reboot to recovery and apply the update, it booted with Chinese text in recovery boot and failed with just one word - "Error". I'd imagine that's because recovery.img wasn't part of the bundle, so my watch still has the Chinese ROM recovery on it. Looking at the update.zip, it's fairly clear it's built in English - with English error messages in "updater-script".
I'm hunting around for the English ROM's recovery image, and will probably find it in the next few minutes, but figure I should mention this hole - and that this routine is also useful for converting to English. It'd been demonstrated before that you can run the English ROM just by flashing it (and boot.img), but no unified thread seems to exist for it yet (that I can find via Googling at least). :good:
edit: Literally 5 minutes later, bam. https://forum.xda-developers.com/showpost.php?p=71264431&postcount=599 - I downloaded that Fix_recovery bundle, pushed it to /data/media/0/ from the mod recovery, ran it, and it gave some errors but fell back to the "dd" method. So, all that's needed to get a complete English ROM flash is to add recovery.img and the line:
Code:
busybox dd if=recovery.img of=/dev/block/platform/jzmmc_v1.2.0/by-name/recovery bs=4096
Hi All,
I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.
I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?
Thanks
Dimitar
dpenevdpenev said:
Hi All,
I have just received my watch from a BT/WiFi issue repair.
I am not sure if they have fixed it as starting the watch and
I am getting "Unfortunately the launcher has stopped" message.
I do see the charging indicator but this is pretty much the only thing I see.
If I reboot pushing the button I get to the same point.
I see that this is an old problem. How do you guys fix this?
I do have adb shell access. Can I somehow reset to factory default using adb?
Thanks
Dimitar
Click to expand...
Click to collapse
You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.
Neuer_User said:
You can boot into the bootloader (fastboot) with "adb shell reboot bootloader". Then in fastboot you can tyoe "fastboot -w continue". That will boot the watch normally, but clear cache and all userdata.
Click to expand...
Click to collapse
Thanks Neuer_User,
what I did:
1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above
Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"
This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.
Thank you once again.
dpenevdpenev said:
Thanks Neuer_User,
what I did:
1. I have entered Fastboot as you explained. Fastboot logo on the watch
2. :~$fastboot devices
0123456789 fastboot
:~$fastboot -w continue (this in the Linux bash shell)
resuming boot...
FAILED (status read failed (No such device))
finished. total time: 6.395s
:~$
The watch reboots due to above
Or should I enter fastboot watch shell first?
The above procedure doesn't help.
Still I get "Unfortunately the launcher has stopped"
This should be on the original Chinese ROM 1.2.9 as far as I remember. It was long time ago I ship the watch to China for repair.
Should go to Pace ROM. what would you advice.
Thank you once again.
Click to expand...
Click to collapse
Hmm, if that doesn't work, try "fastboot erase cache" and "fastboot erase data". That will really completely delete all user and cache data. The next restart should take a long time.
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?