Hi
So yesterday I was trying to install TWRP recovery in order to install Cyanogenmod 11 on Xperia S , I followed a tutorial on techglen, the problem is that now I only have the recovery on my phone , it boots instead of the system , the system files are still there but I can't boot on it , If i connect my phone to my computer I can't access the storage even if I mount it using TWRP
So i have some questions
Is my phone broken?
Instead of flashing a .elf file i flashed the .img instead , is that the source of the problem? ( i didn't do it on purpose , but i didn't pay attention :/ )
can i flash the boot.img of the old system to get it back on booting ?
If there's a way of pushing the CM11 into my phone and installing it would that fix my problem?
Can i use flash tool to flash my old system back ?
Related
I seem to have soft-bricked my one-v and could really use some pointers.
The things I did to get the phone bricked:
- Unlock the bootloader
- Try to flash miui.
Since this attempt the phone only boots until the "quietly brilliant" screen appears (with a red "This build is for development purposes only..." warning, but I guess this just indicates the bootloader is unlocked right?)
Since then I have installed ClockWorkMod recovery image. This seems to work, I can get in recovery mode and do things like install specific zip files from sdcard.
Unfortunately whatever ROM I try to flash the result is the same: boot until the quietly brilliant screen and then nothing.
For instance, I tried to flash shpongle_primou_20130521.zip (the One-V is the GSM version) using the following steps:
- Download the above zip file
- Extract boot.img
- Copy the above zip file to sdcard using another phone (cannot boot with the one-v so I cannot use it to write to sdcard)
- Put the sdcard back into the One-V
- Start the phone in fastboot mode and connect to USB
- use fastboot to flash boot.img (flashboot flash boot boot.img)
- Switch to recovery mode
- Use ClockWorkMod to flash the zip file
- Reboot the phone
Result: hang in quietly brilliant screen. If I just let the phone alone it seems to reboot every 5 minutes or so.
I fear that I am doing something stupid due to a lack of understanding of some basic concept. Can you guys give me some pointers on how to proceed to unbrick the phone?
it seems u have not flashed the correct kernel for shpongle (the boot img inside zip doesnt work)
try this kernel (ONLY FOR SHPONGLE) http://www.mediafire.com/download/vj8vv8hjyhzg3xv/boot-HELLBOY-42-201305202359.img
Also do factory reset from recovery everytime u flash a rom( u can backup data via titanium backup)
Also, your command command should be fastboot flash boot boot.img.
Sent from my HTC One V using xda app-developers app
Awesome, I got SHPONGLE to work. Installing the correct boot.img and clearing all data did the trick.
Now I can try to install miui again but I have a stable situation (and backup ) to work with.
Thanks a lot!
I have the same issue with my HTC one V but it is the virgin mobile version ( I live in the east coast of U.S.A.)
Will I be able to use the same solution?
which is the right ROM and Kernel for me?
Hello!
My Oppo Find 7 (international) seems to be bricked.
I'm on stock ROM COS 1.2.5 with stock recovery 1.0
After booting it stuck in the Setup-Wizzard with "settings has stopped"-Loop.
Unfortunately in stock-ROMs the USB-debugging is disabled, so i can't acces via adb fastboot to flash other recoverys.
And cause of the loop i can not enable USB-debugging...
The recovery (stock 1.0) let me only flash 1.2.5, no other ROMs work.
Things that work:
- entering fastboot (but no access via adb as i wrote)
- entering recovery and execute "zip from sd" (while sd means only internal sd here)
- normal boot to the f****** Setup-Assistant, enter PIN. At slect Language the "setting has stopped"-loop starts
- while the device is in loop, i can access the internal and external SD-card via PC, copy and delete files works
Please, has anybody an idea what to do ?
Thanks to all
Marco
Since you can get into fastboot, download a custom recovery, go to fastboot, type
fastboot flash recovery x
Replacing x with the full name and extension of the file, and install a ROM. Alternatively, if you want ColorOS, try downloading 1.2.4i, and installing it through the stock recovery. Then you can update from there
Hmmmm....
Positive! At this moment i learned that USB-debugging is needed for adb-access on a booted device, not for fastboot-access
Yes, i could flash TWRP via fastboot (puuhh, not bricked)
THANKS !!
Now i can mess around the "settings has closed"-Loop, wich is still in place.
(No wiping fixes the problem, even 1.2.1 nor 1.2.3 or whatever)
But i'm on the road again and can check out fixes.
Thanks again!!
That's weird. Did you ever install custom ROMs before having this issue?
Did you try formatting System in TWRP? But be careful, when you format System you have to install stock Color OS BEFORE rebooting your device. That means stay in TWRP after you format and install the ROM, then reboot.
Hello friends
I had a problem with the mini z11, I have a hard brick.
I wonder if there is any recovery rom, or if the official serves me.
I can flash by nubia Toolstudio?
the terminal does not turn black screen on or enters recovery, flash a rom confusion mini z9.
I need help please, if you recognize the terminal QHUSB_BULK is hope.
Thank you for your interest, Greetings
Still a little bit early for Z11 Mini...
Did you unlock bootloader, rooted and installed some recovery?
Bricked device nubia z11 mini
Hi Guys,
I was looking to update the Nubia to v 2.04 from 1.40 so I used flashify to flash the stock recovery (worked earlier) but the system went dead.
I used tool studio to get the recovery back but now it is not reading my internal storage where the files are kept, it suggest mount error with system, data etc .... so what could be a way forward?
pratikbr9 said:
Hi Guys,
I was looking to update the Nubia to v 2.04 from 1.40 so I used flashify to flash the stock recovery (worked earlier) but the system went dead.
I used tool studio to get the recovery back but now it is not reading my internal storage where the files are kept, it suggest mount error with system, data etc .... so what could be a way forward?
Click to expand...
Click to collapse
Just flash twrp from pc and go to recovery
Then mount usb storage and copy the rom.zip and flash it
moha07 said:
Just flash twrp from pc and go to recovery
Then mount usb storage and copy the rom.zip and flash it
Click to expand...
Click to collapse
Now I have flashed rom v 1.32 , it is showing splash screen but it hangs at "Be Yourself screen", adb is also not detecting the device to install twrp through pc. Please share some detailed guideline.
pratikbr9 said:
Now I have flashed rom v 1.32 , it is showing splash screen but it hangs at "Be Yourself screen", adb is also not detecting the device to install twrp through pc. Please share some detailed guideline.
Click to expand...
Click to collapse
Follow this guide to flash twrp, use the vendor id from below guide
https://forum.xda-developers.com/android/development/recovery-unofficial-twrp-3-0-2-zte-t3550995
Then u flash the rom.
Before flashing the rom, wipe everything expect internal storage and sd card
Need persist.img
Hi,
Have got to know persist.img is corrupt. Hence, flashing is happening but no booting even twrp is not helping. Persist.img is usually found in fastboot img of the rom which helps to install rom in fastboot mode. Kindly do let me know if I can find fastboot.img of Nubia z11 mini.
Thank you
Hello guys,
i have the same brick mode as the op.
The system doesn't recognize the mobile, it only shows it as QHUSB_BULK and it keeps disconnecting.
What are the steps to follow from the pc?
I found somewhere one software called one click unbrick but when i try to install the drivers with it it says that "the system policy has been modified to reject unsigned drivers".
If i can take it to the place where the phone is recognized as a storage from the pc then i can take it from there.
Thanks
Unbrick and downgrade
I once brick my nubia the same way. BUT NOW ITS ALIVE AND WORKS FINE (sulking why didn't I bought the ZUK 2 even though at the time i bought z11mini they were similarly priced)
UNBRICKING:-
ALL you have to do is download the same firmware which was installed prior to the rom to which you downgraded to [ simply put if you had v2.40 running before and tried to install v1.40 then download the v2.40 rom for flashing), once downloaded {USE A PC OR MAC TO DOWNLOAD THE ROM OR ELSE IT MIGHT GET CORRUPT} copy it to the root of an sd card(2gb upto 32gb; sdxc cards may not work), insert the sd card into the phone , then press and hold the power button until the phone reboots, as soon as you see the bootlogo press and hold vol- and power keys simultaneously, you wold boot into nubia recovery now select update from sd card confirm and let it install as soon as update finishes your phone will boot back up normally. [UP TILL THIS POINT NO FILES WOULD BE LOST].
NOW YOUR PHONE WILL BE WORKING AGAIN.
DOWNGRADING:-
YOU DON'T NEED ANY EXTERNAL SOFTWARE FOR THIS
JUST DOWNLOAD THE ROM U WANT TO INSTALL AND PLACE INTO SD CARD AS ABOVE.
TAKE A BACKUP AND SAVE ON A PC, ANOTHER PHONE OR ANOTHER SD CARD{not the same one} OR ANYWHERE ELSE SAFE cause after this everything inside your phone will be DELETED.
BOOT INTO RECOVERY as STATED ABOVE.
-ATTENTION- DON'T install the rom as yet.
FIRST WIPE cache and data.
SECOND- INSTALL THE ROM SIMILARLY AS PRESCRIBED ABOVE.
THE SYSTEM WILL INSTALL AND REBOOT.
ENJOY{but why are you so eager to downgrade your system, i was once as well but after downgrade to lollipop.....nothing......performance was same as on Marshmallow.
ADVICE- for some reason the ota updater never shows any new updates, you will have to download updated roms from nubia website to install using recovery{the app has option to apply local update but it does nothing and gets stuck on nubia logo, u will have to restart your phone after that}, as long as you are installing updates u don't need to wipe data and cache and also your files will remain intact. BUT TO THIS ONLY EXCEPTION IS V2.06, on this you do not need to wipe data and cache but the rom itself will wipe all data on your phone so be careful. :good:
NUBIA Z11 mini is Dead
pratikbr9 said:
Hi Guys,
I was looking to update the Nubia to v 2.04 from 1.40 so I used flashify to flash the stock recovery (worked earlier) but the system went dead.
I used tool studio to get the recovery back but now it is not reading my internal storage where the files are kept, it suggest mount error with system, data etc .... so what could be a way forward?
Click to expand...
Click to collapse
I Have the same problem in my Nubia z11 mini , its already dead only it recognize when it connected to PC as QHSUSB_BULK ,
i have tried to flash through QFIL but no use ,
View attachment 4753025
pratikbr9 said:
Now I have flashed rom v 1.32 , it is showing splash screen but it hangs at "Be Yourself screen", adb is also not detecting the device to install twrp through pc. Please share some detailed guideline.
Click to expand...
Click to collapse
Please tell me how to flash TWRP with this condition my device recognize only QHSUSB_BULK in the device manager ,
NO boot loader and recovery mode
Hello,
I am having a problem where my phone is only, as far as I can tell, willing to boot into recovery. From the system, doing a normal reboot ends up in recovery, from powered off it goes into recovery, rebooting from recovery to system ends up back in the recovery, and the fastboot menu's "Continue" option goes reboots to recovery. The only way I can get into the system is to boot via fastboot -- i.e.,
Code:
fastboot boot boot.img
Where boot.img is the one packaged with the rom I am currently running.
This is not convenient because I need to connect it to a computer!
Is there some way to tell the bootloader to not boot recovery by default?
I have tried simply flashing the boot.img from above with:
Code:
fastboot flash boot boot.img
Which doesn't have any noticeable effect.
I suspect I broke something last night kicking around. I flashed the Open Beta 10 Modem & Firmware, then flashed the Open Beta 10 recovery, before changing my mind and installing TWRP 3-28 and Resurrection Remix v5.8. Somewhere in there, fastboot -w got run, but I don't think I did anything else potentially destructive.
Thanks for reading!
Hmm... Try install boot into recovery partition and recovery into boot? I know it's sound like a joke, but it will probably help you while u wait for a beter solution or just solution to repair that problem.
Anyway - maybe try flash old MM firmware?
A solution for me...
For anyone who rolls along and sees this in the future, my fix was:
0. Take a backup of sdcard AND data -- Step 2 will wipe data and sdcard without asking
1. Download the official recovery for the OnePlus 3
2. Use fastboot to boot (I didn't even have to flash) the official OnePlus 3 recovery AGAIN: WARNING: This step wipes all data without asking for confirmation!!!
I have now installed TWRP-3.0.4.0 and Resurrection Remix v5.8.1-20170202 and everything seems to be working just fine.
Thanks to @sylviohneto for finding this fix here: https://forum.xda-developers.com/oneplus-3/help/critical-bootloader-boot-recovery-fresh-t3530283
I had same problem so for that just take nandroid backup of data and while in turn copy it to pc and any other backup of data you need then format all the partions and reinstall rom and restore data... And if your lock screen have security then check Google you will have to delete a file called locscreen.db from file manager in twrp to access your phone
hi,
my oneplus 3 has been rote since i got it (i bought it on launch day) but since i updated it to the beta 19, my phone is no longer rooted : when i put the phone in fastboot it says that my bootloader it unlocked but all the apps who requier root are saying that the phne is not rooted and i cant get twrp to work. i tryied with the official app on my phone and with a program called "tool all in one" (https://forum.xda-developers.com/on...ol-tool-one-driversunlocktwrpfactory-t3398993) and when i flash twrp from the program, i can boot into twrp but then i can't access my files and after i boot the phone, i can no longer boot to twrp
does anyone have a solution that doesn't involve me wiping the phone?
You loose root after updating. Try installing twrp again and then rooting it. Use the toolkit for oneplus 3. Simplifies the process
what do you mean by "then rooting it" ?
the program i use does the same thing as the toolkit and when i install twrp, as i said, it can boot on twrp one time and in twrp i can't access my files and after i boot the phone i can't get back to twrp ,i get the stock recovery
Unless your ROM has built-in root, after flashing TWRP, you have to flash SuperSU or Magisk to obtain root. Mere flashing of TWRP will not give you root.
I know but i can't get to the folder when the magisk file is : when in boot into twrp i cant see my files
Few details... it's quite difficult to help you.
What's the root method? Magisk, SuperSU or Kingroot? Which version?
Ps TWRP recovery is not depending by root, you just need to unlock bootloader (surely it's already unlocked) and flash the same recovery, from PC, via the command "fastboot flash recovery filename.img".
Now enter in TWRP:
1) Wipe /system and /cache;
2) Flash another time Open Beta 19;
3) Flash Magisk or SuperSU (be sure to have latest release);
4) Move TWRP img file from computer to device, then flash it another time (because firmware provides the OOS stock recovery);
5) Reboot and wait 5-10 minutes, because of cache rebuilding.
Tell me if you solve
I am using magisk
Yes my bootloader is unlocked
My problem is that when i flash twrp i cant access my files so i don't want to wipe system if i cant reflash something after
I think that I'll wait for the next update, maybe then it will work
But thank you for your help
Which version of TWRP do you have? Try eng.stk's latest version.
I tryied 3.1.1-2
The eng.stk is not available anymore
Your phone is encrypted, so you have to format data ( but your internal storage wiped by formating data, so back it up ,then only twrp read files in your storage)and flash custom kernel then boot restore backup .
how do you know that my phone is encrypted? i never encrypted it
i use titanium backup so i can't back my phone up until i get rot back
Whenever you flash stock ROM it encrypt if you boot into system directly . So twrp could not read internal storage. Whenever you flash stock ROM you must flash custom kernel or any other method to avoid encryption. This is happened to me and what I'd done is flash custom kernel before boot into rom
To save your data try this
https://forum.xda-developers.com/oneplus-3/how-to/unencrypt-oxygenos-loosing-data-t3412228
Who said that? Check this: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Edit: If you want to save items in internal storage, you can use ADB commands instead of TWRP. You can also simply copy and paste if your PC recognises the internal storage of your phone.
I succeeded but i had to clean everything and use the last backup i made a week ago
Thank you all for your help