Related
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Which modes can you get into?
TWRP allows you to mount USB OTG. Try flashing something from there.
Press Thanks If I Helped You!
Sent from my dead Nexus 7 2013 LTE! ???
Yes, like aniket0317 wrote: if all else has failed, put a ROM on a flash drive, connect it with a USB OTG adapter, and use TWRP.
I've lately had trouble getting my N7 recognized while in recovery mode, though everything's fine while in the bootloader and Android. But with TWRP it's easy to mount external flash storage and install from that.
RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
are you able to go into fastboot mode? if so you still have hope
kmaq said:
are you able to go into fastboot mode? if so you still have hope
Click to expand...
Click to collapse
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery
RecklessBrandon said:
So I'm an idiot. I deleted everything off my Nexus 7 then I was going to flash to a new ROM, didn't work, I don't know why but it won't install. I have nothing else to install, not any other ROMs and no backups. To make the whole entire thing worse, my Nexus wont connect to my computer. Before you say to reinstall the drivers or plug it into another computer, I have, I've tried everything and nothing works. So my question is; Am I screwed or is there somehow a way to install a new ROM (seems impossible) or put the stock ROM back on? I tried the adb sideload method but I was completely unsuccessful as well as every other method I've seen/could come up with. After trying weeks to get anything back on my Nexus 7 I'm just about ready to toss this paperweight in my drawer and forget abaout it
Click to expand...
Click to collapse
RecklessBrandon said:
I'm not allowed to post pictures yet but I believe I can get in fastboot mode and I am sure that I can get into ClockworkMod Recovery
Click to expand...
Click to collapse
download the 4.4.4 image
go to fastboot mode, connect the usb cable to laptop/pc
open command prompt and go to the folder where you have extracted the 4.4.4 image
fastboot oem unlock
type flash-all.bat
if all goes well device should reboot (initally will take some time) if it took more time, reboot again into fastboot mode
this time you can try manually commands one by one
in the folder where you have extracted the 4.4.4 image you will fine "image-razor-ktu84p.zip", extract this zip file as well
execute the following commands one by one:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot reboot-bootloader
fastboot flash bootloader bootloader-flo-flo-04.02.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot reboot
device should reboot and if it displays language screen then cool complete the wizard, reboot in to fastboot mode again to lock the bootloader
fastboot oem lock
fastboot reboot
and enjoy!!! do report back what happens.
fastboot -w update stockrom.zip
I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.
How does it appear in Device Manager? Have you downloaded and installed the drivers?
http://developer.android.com/sdk/win-usb.html
RecklessBrandon said:
I'm a little confused on the instructions, also, as mentioned, my Nexus isn't recognized by my computer no matter what I try.
Click to expand...
Click to collapse
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?
I am having the exact same problem, it was installing got stuck on "erasing userdata" for over 2 hours and now nothing will work except for fastboot, and some how the device locked itself again. Only thing i can get to is fastboot mode, the computer recognizes the device. When I try to unlock it, it gets stuck in "erasing userdata" I let it run over night last night hoping it would some how work with no luck. I am unsure of what to do. Is there anyway to install a factory OS without unlocking? Every guide I've searched for has me doing an fastboot oem unlock and then the tablet freezes on erasing userdata. Any help would be greatly appreciated. Thanks!
kmaq said:
in the fastboot mode, after connecting your device to laptop/pc,
if you type "fastboot reboot-bootloader" in the command prompt
what happens?
Click to expand...
Click to collapse
Reread your initial instructions, and it worked! Thank you so much!!!
Rooted my phone using Temporary CWM method, installed Titanium Backup and restored from my old phone. Selected All Apps and Data. Rebooted my phone and I assume that it is now stuck in a bootloop. It gets to the ASUS and Intel Inside screens, then I get a spinning circle forever (well, at least 3 minutes).
Where do I go from here? Reflash the ROM and start over and don't restore system data? Is there an easier/quicker way?
Thanks
Go to fastboot mode by holding the power and volume up button,connect USB cable be sure that you installedmusb and fastboot driver.go to folder of fastboot and hold shift key then right click open command window here and type:fastboot erase cache then enter fastboot reboot and voila..
Thanks for the reply, but that didn't do it.
I was able to execute the commands, but still no luck. I got into recovery to try and wipe from there, but got the dead android. I them held power up and tapped vol up to get into recovery. tried to wipe cache from there and the phone just sat there for 3-4 minutes with nothing. Now when I get into recovery, I get a flashing dead android, and the power/vol up trick doesn't work. I can still boot into fastboot.
Di I just need to reflash the stock image? Or is there something else I can do?
arrosen said:
Thanks for the reply, but that didn't do it.
I was able to execute the commands, but still no luck. I got into recovery to try and wipe from there, but got the dead android. I them held power up and tapped vol up to get into recovery. tried to wipe cache from there and the phone just sat there for 3-4 minutes with nothing. Now when I get into recovery, I get a flashing dead android, and the power/vol up trick doesn't work. I can still boot into fastboot.
Di I just need to reflash the stock image? Or is there something else I can do?
Click to expand...
Click to collapse
I had the same problem as yours and it took 3 hours before i figured it out and managed to run the phone normally.I downloaded all the files,drivers and latest prerooted system img. here in this forum.you can download it there and there is the instruction how to do it.
To Begin :
1. on Fastbootmode connect your device and on the flashtool folder hold shift key and right click and go to open command here,be sure that downloaded images are in the same folder.Recovery img.,Boot Img. and the big pre-rooted System img.
2. type fastboot devices then hit enter key - the device nos. should appear and you can start now to flash...
a. fastboot -w then hit enter this will erase the system
b.fastboot flash system system.img then hit enter key
c.fastboot erase userdata then hit enter key
d. fastboot erase cache then hit enter key
e. fastboot reboot then hit enter key..
THANK YOU!!!
Thank You, Thank You, 1000 times, Thank You.
I did everything you mentioned, with a few small exceptions
1. Make sure you have the lastest version of Fastboot
2. Instead of step b above, I did the following. Not sure if it was needed or not, but it worked for me
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
3. At the end, after I did a Fastboot Reboot, I got the dreaded dead android again. I nearly cried. However, I rebooted again, and everything seemed to work. Note that on the first boot, it may take 2-3 minutes for the OS to come up.
4. All of the files and great insight can be found here: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance
I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that
Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload
Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.
For those that, like me, could not get driver recognition on the latest Win 10 x64 no matter what you tried. And ,yes, using every tutorial I could find on this and two "other Forums". Odin failed to see my device (still can't) Cydia impactor allows rebooting into fastboot and D/L but doesn't connect in either alt. mode. Yes, drivers all removed and replaced in varying states (usbdeview, etc.).
But ADB/Fastboot works!
Make sure you have your adb/fastboot drivers installed universally (Check this Fabulous Forum)
Download device-specific TWRP - I used this one for the 4gb version - https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
L.Shift-R. click in the folder you downloaded to (Open Command Window Here) - "adb devices" (to make sure device registers) then - "adb reboot bootloader" gets you into fastboot. - "fastoot boot {your-recovery-name}.img"
I got a fully functional TOUCH CAPABLE TWRP. Which I proceeded to load this - https://www.dropbox.com/s/j1owqv7mjkdpo75/UPDATE-SuperSU-v2.46.zip?dl=0 - and, VOILA! ROOT!!
I had similar issues with my laptop and drivers. Used a friend laptop in the end to "see" the phone and install twrp.
Sent from my S7 using Tapatalk
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
vaskovass said:
When I try to boot the recovery.img with fastboot it says that my OEM is locked. I check OEM unlock in developer options, then I do: adb reboot bootloader, then fastboot oem unlock. A warning appears saying to press VOLUME UP button to continue, voiding the warranty or VOLUME DOWN to go back. I try to press VOLUME UP and nothing happens... how did you do it?
Click to expand...
Click to collapse
Hi there, I have the same issue. No success
I found a way, instead of volume up, use the home button this worked for me.. however after I unlocked the OEM and flashed TWRP the phone didn't want to boot anymore. It was stuck on Elephone logo with warning: "Orange State: The phone has been unlocked and can't be trusted. Your device will boot in 5s", however it didn't boot and stayed like that for almost an hour. Had to flash back the stock firmware to boot. Tried 1 more time the procedure to root but again the same. Maybe I do something wrong?
stock fw flash back
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
dnsgtr said:
Hi, please can you help me with how you flashed back the stock firmware?
I get an error message with twrp : invalid zip file format.
Thank you in advance!
Click to expand...
Click to collapse
I read somewhere the is a zip inside the update.zip & is that one that is flash able with twrp.
Have a look
During the main time I managed to flash the 0218 stock rom.
I still got the orange message but the phone finally boot. Then I just called the twrp recovery img via atb. I did nothing only touch the reboot in the twrp screen and since then "Orange status...." again.
May be the twrp recovery img is not the right one...
Bad command "fastoot boot {your-recovery-name}.img"
after OEM alow (informacion phone/compilacion number touch fast 9 times/access/alow oem)
fastboot oem unlock
"fastboot boot {your-recovery-name}.img" for me is fastboot boot recovery.img and all OK
bat still not working (phone not thrust unlocked bootloader cleaning data in 5..4..3..2..1.. and rebot)
Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.
how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.
Thanks for the hint, but I am not happy with the idea of someone playing with my data
1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC
Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.
Any idea? Should I give up?
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.
Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.
If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b
I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.
Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5