I seemed to have lost my recovery but my phone is otherwise working.
I went from CM13 with TWRP, downloaded OS3 from the official oneplus web download as well as the "optional recovery" on the same page.
I wiped data/system/dalvik/cache and flashed the OS 3 zip.
I then flashed the stock recovery img.
Wiped again.
Rebooted to recovery from TWRP and got stuck with the oneplus logo. Completely non-responsive.
Fearing I had softbricked the phone, I started with ADB, got the Qualcom HUB listing under Device Manager and was about to start the process of updating Qualcom Drivers and running the recovery tool (having not been able to get fastboot to see the device) when a miracle happened and the phone started booting up on its own. After running setup, I rebooted, no problem.
I have since been able to use fastboot oem lock and confirmed the phone is locked (I wanted to get back to stock).
Everything is working fine EXCEPT I don't seem to have any Recovery at all. If I use the Developer Option for Advanced Recovery and boot into recovery, I get the oneplus logo. If I use Vol Down and Power I get the oneplus logo.
I think I have lost my recovery but recognise that I am out of my depth and don't want to stuff up the second chance I was given by trying to flash a recovery (I want stock receovery so I can get OTAs in the future). BTW, I read extensively before I tried this, looking at a number of different sites and followed instructions to the letter (or at least I thought so!).
Could someone who knows what to do please help to get my recovery back? It would be very much appreciated.
Edit: I managed to fix it. You have to use the Qualcomm tool and go back to OS2.2 and then update to OS3. See the link below and follow Method 1, doing everything exactly as set out.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Related
Hi Guys,
i have a very specific issue.
Its HTC hero which been upluged before finishing official upgrade to froyo.
So, where is the problem?
Hero cant boot, all the time just stay stucked on "HERO" boot animation. The problem is, that it was upgrade from stock Eclair to stock Froyo. They didn't have any root, or recovery (CWM, RA, nandroid)...
The phone can be started in hbot, fastboot, stock recovery.
HBOT->
I've found this > http://forum.xda-developers.com/showthread.php?t=575448 < but i think its need a function hero to set up setup.
So there is no way i think
Fastboot->
I've try to flash recovery with AR, CWM via
"fastboot flash recovery recovery.img"
but only get this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stock recovery->
I've also try to flash via "apply update.zip from SD card" from this
http://www.modaco.com/topic/291942-22jan-stock-roms-radios-in-updatezip-format-for-gsm-hero/
every single file crashed "E:Verification failed!"
I'm such a big noob, but is there any way which i didn't try? Something like flash CWK recovery mode via update.zip? Every idea can help.
Thanks
Do you have your hero drivers set up on your PC?
Also, when flashing recovery.img using fastboot, please rename your clockworkmod.recovery.blablabla.img in recovery.img and then try to flash again.
as i thought so
prntscr.com/aun85 <its a link, but i'm newbie here, so i have a constraints
but its exactly the same as the file was named clockwokrmod.....img
Driver should be ok (get from android-cellphones com)
Q: how can i access the adb? In device manager a use this driver. But in cmd "adb devices" cannot find my hero. But idk if it helpfull.
Sorry for my english
When your phone is plugged in your windows PC (in hboot mode), check that the driver installed is called My HTC (in device manager), then download the latest RUU under HTC Hero support site (not the 2.1 one) and run the program, it will erase everything, but if it is successful it will install the 1.5 system to your phone, and you can start over
Sent from my GT-I9100 using xda premium
Problem was solved via hboot mode. Thx guys
Hi everyone,
Yesterday, I tried the 4.4 OTA on my wifi Nexus 10 (unlocked but not rooted, previously 4.3), but got an "Error!" screen, and now the device seems soft-bricked (can't boot into system, get a "No command" screen, but I can get the bootloader screen with Power + both volume keys).
After some investigation, I tried restoring a factory image using Nexus Root Toolkit v1.7.8, after recharging the device a full night. I used the "Flash Stock + Unroot" with "Soft-bricked / Bootloop" option. At first everything looked fine, but I'm now stuck at "writing system" step, for 30 min now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The strange thing beeing, the device shows "Fastboot status - okay":
Might it be a sync status problem between NRT and the device? Is it safe to stop the operation and try to reboot my Nexus?
Thanks for your help.
Hi. I have the same problem.
How did you manage to solve this?
Regards
Hi,
Yes I did.
I was still stuck in the "writing system" test, and rebooted the device. As I feared, the system didn't boot, so retried the stock kitkat flash through NRT. The second pass got me to the same result, stuck in "writing system" with the device saying "fastboot okay".
I decided to reboot to recovery, and wiped both system and cache partition. When I reboot, I was able to see the kitkat startup screen, and then everything went fine.
Eventually, I'm not able to tell what went wrong or good with the flashing, but here are my observations and facts :
- once launched, the system initialized correctly, and I didn't encounter any problem since then
- even if the system partition appears to be flashed correctly, I was still amazed that everything works, since the user partition hasn't been written
- only the stock system has been installed. No root nor custom recovery.
As for the root cause of the initial OTA problem, I think it was caused by lack of battery power.
Hi
i was stupid enough to unlock my bootloader and flash recovery, then reflash back latest meizu stock via twrp , and flashing again the twrp recovery image,
i don't why, but the first init of the rom update ****ed my recovery up and now i lost recovery (even the stock, the phone just booting to the rom)
fastboot oem unlock isn't possible because i'm on locked bootloader rom.
i tried to flash the recovery via rashr with the backup i made and i can't becuase of busybox, i guess it's because the bootloader lock
is there any script or way that i can stock recovery back?
actually if lost the rom i lost my phone....
please help!
UPDATE: STILL WITHOUT SUCCESS TO FLASH THE RECOVERY BACK
i tried adb shell flashing, susscessed to flash system image , but via this method ( dd - of)
https://forum.meizufans.eu/topic/25...ional-firmware-on-your-chinese-mainland-meizu
ir flashed the system partition successfully but without the bootloader nor the recovery
but as it supposed to be , it won't flash recovery , when i'm doing the same for recovery i'm getting Operation not Permitted
hello try this link maybe it solve your problem good chance
https://forum.meizufans.eu/topic/5335/bricked-pro-5
i get token sign failed what should i do now?
prodaz said:
hello try this link maybe it solve your problem good chance
https://forum.meizufans.eu/topic/5335/bricked-pro-5
Click to expand...
Click to collapse
i get token sign failed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what should i do now?
i found a new link for you try this method. tuto is in english and chinese there are some tools and pdf file to help you.
https://mega.nz/#F!R8dSiT5T!08LHl2JKm5_u579uyAWfEw
Its the same!
Edit: I was wrong.
Up
deliad said:
Up
Click to expand...
Click to collapse
Any news on the phone's recovery?
I have the same problem... locked bootloader and TWRP that is not loaded...
just try this.good luck man.http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
tzzzz said:
just try this.good luck man.http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
Click to expand...
Click to collapse
nothing has changed
error token signature
Up
HI GUYS, please join to the discussion:
iv'e opened an investigation thread on the android general hacking forum, so, maybe we can get help from the devs / hackers on xda, because here i don't see anybody that listens to our problem.
http://forum.xda-developers.com/android/software-hacking/pls-help-to-meizu-pro-5-to-life-t3494293
Hello guys! Happy xmas! I've tryed install the CM13 in my smartphone and i had a problem during the install. The cellphone just start in fastboot mode and i lost my TWRP. I can't install any custom recovery and any another custom rom. For now, i'm installing UL-Z00L-WW-1.17.40.1531-user firmware and this problem appear:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can u guys help me?
What I would do:
step 1
make a FULL partition dump, backup all files including modem modemst1 modemst2, which contain the important imei specific to your phone
step 2
charge phone battery to full, download all available versions of updates from asus, copy all to sdcard, install/update one by one, until the latest. This ensures you get the latest modem firmwares.
step 3
root, unlock the phone
step 4
complete step 1 again, yes!!!! it must be done.
step 5
install custom recovery (twrp), then install cm13
VERY IMPORTANT: backup always and frequently, flashing Asus updates or custom rom can easily corrupt the EFS partitions (modem, fsg, modemst1, modemst2)
if u have computer, then adb sideload the firmware file
select update from adb
command - adb sideload filename.zip
be confirmed that the adb drivers are installed for ur mobile
So, guys, i tryed this methods but does't work :/
I'm trying now install a system.img but i'm stuck in this problem:
Can u help me?
TitoSni said:
So, guys, i tryed this methods but does't work :/
I'm trying now install a system.img but i'm stuck in this problem:
Can u help me?
Click to expand...
Click to collapse
use sideload method in stock recovery
Hi. I am facing an issue with my oneplus 2 device, I wanted to make it boot multiple ROMs so searched on google about this and I found a thread on this website only, and in that thread, there was a recovery and zip file given to flash so I booted into TWRP recovery and flashed the zip file first and then recovery and then reboot-->recovery, after that oneplus logo with "powered by android" text came and for 5 mins nothing happened. I connected the phone to my computer and typed the fastboot command-"fastboot reboot recovery", it reboot and stuck at the same state as before, then I used-"fastboot reboot", it rebooted into the oxygen os which was installed on it. then I flashed the original TWRP recovery using its official app as my phone was rooted. After that, I again tried to flash the multirom recovery but this time I flashed the recovery first and then the zip file but the same happened. I again booted into the rom and flashed the original TWRP recovery using the app and then I got to know on the internet that I should first shutdown the phone after flashing multirom recovery and then reboot it in the recovery and then flash the zip file, so I did the same but to my bad luck this time also same happened and this time I am not able to boot into the rom also and I am only now able to use fastboot and to the very worst my bootloader has also got locked I don't know how but it was unlocked last time but when I saw in fastboot it was saying that bootloader is locked. Please help me to fix my phone I have attached the multirom recovery file and the link to the thread. Please tell me if you all want any other info I will try to provide you that.
LINK TO THE THREAD:-
[MOD][FEB-28][TESTING] MultiROM v33 for OnePlus 2
TLDR: MAKE A BACKUP. Seriously. Downloads in second post. Flash recovery, then kernel, then MultiROM. A kernel with the kexec-hardboot patch doesn't exist as of now. It is being worked upon be me Introduction This is a port...
forum.xda-developers.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}