Hi all,
My Nexus 10 seems to be hard bricked.
Here the symptoms:
- Can sometimes be put in bootloader mode
- In bootloader mode, no way to put into recovery mode (the buttons vol up/down do not change the mode = it stays onlw in "Start")
- In bootloader mode, fastboot does not show the device (and of course no way to flash)
- Of course, no OS installed and no way to boot properly
The device seems to be recognized as "Samsung Gadget Serial"..
Any help is welcome !
Thanks
OK FORGET ABOUT IT
I found how to put in recovery mode : press power and BOTH volume UP and DOWN at the same time.
opolette said:
Hi all,
My Nexus 10 seems to be hard bricked.
Here the symptoms:
- Can sometimes be put in bootloader mode
- In bootloader mode, no way to put into recovery mode (the buttons vol up/down do not change the mode = it stays onlw in "Start")
- In bootloader mode, fastboot does not show the device (and of course no way to flash)
- Of course, no OS installed and no way to boot properly
The device seems to be recognized as "Samsung Gadget Serial"..
Any help is welcome !
Thanks
OK FORGET ABOUT IT
I found how to put in recovery mode : press power and BOTH volume UP and DOWN at the same time.
Click to expand...
Click to collapse
Seems an hw problem...
attempted downgrade to kitkat failed -flash-all.bat unable to find boot.img
roscio1975 said:
Seems an hw problem...
Click to expand...
Click to collapse
Hi Guys,
I'm a newb to XDA-developers.
I'll start from the beginning. downloaded image of kitkat from developers.google.com. and abd tools. Typed the fastboot oem unlock in the cmd line and wiped the cache and date/factory reset.
following this I then restarted the tablet and ran flash-all.bat.
On doing this the following was stated in the cmd line:
erasing "recovery"
OKAY
******Did you mean to fastboot format this partition?
erasing 'system'...
OKAY
******Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY
sending 'bootloader'...
OKAY
writing 'bootloader'...
OKAY
rebooting into bootloader...
OKAY
(at this point the tablet restarts)
<waiting for device>
error: update package missing boot.img
I am now left with it continually with the droid on its back no matter what option I select apart from power off.
If it helps, here's the device info
Product name: manta
Variant: wifi
H/W VERSION: 8
BOOTLOADER VERSION: 8
CARRIER INFO: NONE
SERIAL NUMBER: iT STATES IT
LOCK STATE: UNLOCK
REBOOT MODE FLAG: NONE
Its the none that really worries me
Please help!!!!!
Thanks
I'm having issues with my recovery after flashing the OOS 3.0 to the phone. My phone is working but when i boot into recovery, it stays on the page saying 1+ powered by android. Anyone else have this issue, or any ways to fix it.
I also tried re-flashing twrp, but i get "FAILED (Remote: dtb not found)" when i try to boot the recovery image.
FireForged said:
I'm having issues with my recovery after flashing the OOS 3.0 to the phone. My phone is working but when i boot into recovery, it stays on the page saying 1+ powered by android. Anyone else have this issue, or any ways to fix it.
I also tried re-flashing twrp, but i get "FAILED (Remote: dtb not found)" when i try to boot the recovery image.
Click to expand...
Click to collapse
u need modified twrp, here is the link: https://www.androidfilehost.com/?fid=24459283995297945
flo071 said:
u need modified twrp, here is the link: https://www.androidfilehost.com/?fid=24459283995297945
Click to expand...
Click to collapse
After using this twrp, and flashed with cmd: fastboot boot recovery.img, I return in twrp-recovery.
So I restart (with disable and/or not disable to change the recovery). But after that I am in the same situation. It is possible to flash the same twrp for another time but that is not what we want
This even doesn't work when I restart to recovery.
Is there another possible solution?
Thanks in advance.
retaliator said:
After using this twrp, and flashed with cmd: fastboot boot recovery.img, I return in twrp-recovery.
So I restart (with disable and/or not disable to change the recovery). But after that I am in the same situation. It is possible to flash the same twrp for another time but that is not what we want
This even doesn't work when I restart to recovery.
Is there another possible solution?
Thanks in advance.
Click to expand...
Click to collapse
i disabled reflashing the original recovery...whats is asked when you reboot in system...
for me this worked....
Thanks for answering me.
I did also disabling reflashing new recovery when reboot in system.
When reboot in recovery the 1+ logo apearred and nothing happens.
I have the same issue - I can get fastboot and flash recoveries, but the OP2 never gets beyond the boot screen. tried flashing different recoveries, no joy.
---------- Post added at 09:43 PM ---------- Previous post was at 09:02 PM ----------
update - got it working.
steps:
flashed recovery.img in this post.
booted into twrp
flashed oldmodem5.1.1 zip I had on my phone
rebooted into recovery
flashed twrp3.0.2.img
flashed new+modem.zip
flashed exdodus nightly
boom, back in business
you can keep that OOS rubbish
my phone also not going past the 1+ logo screen
as told i downloaded the recovery.img from above
restart my device in fastboot
C:\Users\imran\Downloads>fastboot oem unlock
...
OKAY [ 0.005s]
finished. total time: 0.006s
after this command my device again started n struck at that logo i restart again in fastmode to check
C:\Users\imran\Downloads>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.073s]
finished. total time: 0.074s
please help
Hello, i've the solution
Download the FirstAid :
http://forum.xda-developers.com/devdb/project/dl/?id=16684
- Unzip files
- Boot your phone in Fastboot
- Go to Firstaid_v_2_0 -> Firstaid -> then lunch ' firstaid'
Thanks for the reply..
i run the file but still no use
F:\Firstaid>fastboot oem unlock
...
OKAY [ 0.016s]
finished. total time: 0.016s
F:\Firstaid>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
F:\Firstaid>fastboot flash recovery TWRP.img
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 1.047s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.063s
NOTE:if i enter command "fastboot continue" my device is getting started...
Try this, I think you bootloader is still locked
fastboot -i 0x2A70 oem unlock-go
Or follow this guide
http://forum.xda-developers.com/oneplus-2/general/guide-make-oneplus-2-adb-devices-t3218332
Sent from my ONE A2003 using Tapatalk
I had this problem and got the recovery working again with the modified version from above. Where did you get this? and what modification was needed? This is very strange. I never had that kind of a problem.
I flashed my phone back from OxygenOS 3 beta to OxygenOS 2.2.1 to get a working phone again and will now try to revert to the normal recovery again. From there I hope to get twrp 3.0.2.0 and cyanogenmod 13 to work.
UPDATE: normal twrp 3.0.2.0 works again. So my steps to recover from a brick with no accessable recovery to a working phone were:
1. flash modified recovery
2. boot into recovery
3. flash latest stable stock rom
4. flash latest stock twrp
Thanks a lot dude it worked for me
Keep up the good work guys.
What I did to get a working recovery:
1. flash modified recovery from first post in this thread with flashing recovery from pc
2. boot into recovery
3. flash latest stable stock rom
4. flash in recovery the latest recovery from first post
5. flash beta version Oxygen3
6. flash again twrp in recovery
7. flash superuser
8. disable replace recovery
All is well done.
Thanks for helping me mates!
I found out that it is enough when you:
1. copy modified recovery from first post in this thread to your phone
2. flash modified recovery from your pc to your phone
3. boot in recovery
4. flash the recovery you copied to your phone in installed recovery
5. restart with disable replace recovery
Thats enough to do the trick.
I am sorry to reply to an old post but I am unsure if other people are still having issues with this like I was. Here is some info from https://twrp.me/devices/oneplustwo.html :
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
---------- Post added at 07:19 AM ---------- Previous post was at 07:18 AM ----------
I am sorry to reply to an old post but I am unsure if other people are still having issues with this like I was. Here is some info from https://twrp.me/devices/oneplustwo.html :
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
RUU_A5_DUG_L50_DESIRE_SENSE60_MR_HTC_Europe_2.34.401.1_Radio_1.13.3230.27.0303_13.19.3230.00D_F_release_426496_signed_2_4.exe (LOLLIPOP)
I haven't tested it. Please, use at your own risk.
How to install :
First make sure that your battery is fully charge
- Flash stock recovery
- Boot to fastboot
Code:
fastboot devices
fastboot oem lock
- Now, you can boot your device into fastboot mode again
- And run RUU.exe
Download - Google Drive
Update still sending only and didn't continue
I did all these steps but it stoped on sending (0/6) it didn't continue, why?
My phone : a5_dug
S-off
Cid: HTC__J15 and i made it super cid and tried again but it still sending only again
Bootloader: re-locked
And i installed the stock recovery
What's wrong?
Need some help if someone can do that
- I have oem unlocked my b/l with unlock code, install twrp, try some polished rom but i don't like it and try to go back to oem locked state to flash an RUU file through ADB...
When i go to download/fastboot mode and type a "fastboot oem lock" command i have a message
"C:\adb>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
OKAY [ 0.028s]
finished. total time: 0.029s"
to my PC and on my phone i have a question "Yes to OEM lock and hard reset or No to live..."
I point to Yes and when confirm that my phone rebooted to a loop rebooting and blinking display with HTC logo and red words text...
Whatever i try to do it's always blinking/rebooting
Is there any way to normallise my phone and turn to any normal state?!
TNX
I moved out from previous state!!!
What a luck!
Dont know how but pressed VolUp+VolDown+Power and gone to bootloader state. After that have to unlock b/l again and after that when gone to Recovery, my TWRP is still there what a sweetness....
When enter to TWRP just some quick tex "Decrypting phone" and immediately rebooting to a normal state with all working phone states!
Is there any way to lock b/l again, turn to OEM state and to do a normal/regular HTC updating???
My last HTC update was 1.64.401.10 and European version...
Any advice?
TNX
Flash stock recovery: https://forum.xda-developers.com/u-ultra/development/unlocked-model-stock-recovery-t3585622 and you should be able to lock your bootloader successfully.
Never update with a third-party recovery. After you are done updating, install custom recovery again.
Ok.
I didn't know that
Tnx
Folks,
I have a ZF2L aka ZE551KL which is currently in a bootloop. Why that happened I have no idea as I have not dinked with the stock rom or for that matter even unlocked the bootloader.
A little bit of history, over the weekend, I had plugged in my phone to charge it and then when it completed charging I unplugged it and then tried to reboot it. That was the last time I had it working. After the reboot the phone has been in a bootloop ever since.
In order to try to recover from the above, I started reading a bit on what to do and I came across the postings that mentioned the bootloader has to be dropped to the Lollipop level so that it can be unlocked and then the recovery can be upgraded to Marshmallow. While trying to get all of that done, I have ended up here.
I "think" I have unlocked the bootloader using the command
echo -ne "\x01" | dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo
I ran the above command directly on the phone via the terminal in TWRP. I booted into TWRP using the following fastboot command
fastboot boot twrp-3.2.3-0-Z00T.img
Running the fastboot command, fastboot oem device-info gives me the following output
C:\Users\home\android\platform-tools\images>fastboot oem device-info
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
Finished. Total time: 0.016s
However when I try to flash a new recovery TWRP-3.2.3-0-Z00T I get the following error
C:\Users\home\android\platform-tools\images>fastboot flash recovery twrp-3.2.3-0-Z00T.img
Sending 'recovery' (29856 KB) OKAY [ 1.342s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
Finished. Total time: 1.388s
I'm a little lost on what's going on. The device-info tells me the bootloader is unlocked, however it appears that something else is still locked which is not allowing the recovery to get flashed.
The stock recovery I was on before this all started was asus/WW_Z00T/ASUS_Z00T/6.0.1/MMB29P/WW_user_21.40.1220.2181_20170805. The recovery I currently have is LRX22G.WW_user_1.16.40.763_20151201
Any pointers on what I could do to get this resolved would be helpful?
hi if ur bootloader is unlocked, u an do a fresh flash of all d partitions as sometimes things get messed up on its own.
download firmware from https://drive.google.com/file/d/0B43Ue6xY9MmdN0UzWVRFcno4N0U/view and extract, then run flashall.cmd (in fastboot mode i.e. pwr and vol up)
u should finish without any hiccups. u will lose twrp though
tried on mine it woks. but google frp may be active so keep ur email n pass handy. m not responsible for any damages though ...