Ok, where to begin:
I Rooted this weekend and have been installing a few roms, all has been fine. This afternoon I tried to partition a fresh SDcard using the windows-recover.bat method to allow apps2sd and that (I believe) is where it all went wrong.
When I rebooted the phone it went into a boot loop, never getting past the HTC logo.
So I factory reset from the HBOOT menu and it still looped, until I put a new SD card in - then it loads ok (I'm using Defrost 2.41d) but after the initial set up it says emergency calls only - I manually select Orange (the phone is a factory unbranded/unlocked CPW handset) - it says it's not allowed to connect - won't connect using my T-Mobile sim either.
It also says the SDcard isn't mounted no matter what SDcard I try (tried 4x).
I've tried booting into recovery and installing a zip from the SDcard so try and install a new ROM and it fails saying unable to mount SDcard.
I have also done a cache wipe, and basically any other option that sounds like a wipe type option from within the Recovery menu on HBOOT/Clockword MOD.
I'm lost, if I can't access the SDcard in any way then I'm screwed and can't reflash.
Any ideas gratefully received...
have you tried pushing a rom to the phone from your computer? or unrooting with an official HTC RUU ROM and starting again?
also search the "USB bricked" stuff on the desire android development forum...
Thanks for the advice
I'm trying to push a std Official ROM but the PC just doesn't see there is a phone attached when the phone is in normal use mode, it starts to see it in HBOOT mode but then says the driver has failed etc.
Someone elsewhere has mentioned the USB brick possibility but from what little I've read it requies SDcard functionality and my phone just doesn't see ANY SDcard - even in HBOOT / Clockword MOD recovery mode.
any feedback?
could you solve the problem?
Guys my english is not that good so if you dont understand something tell me.
my friend gave me his phone becouse i had to fix it for him. i thought it was an usual brick, but when i try to flash the rom with odin it fails on the nand writing. when i get in to recovery mode i see that the device doesnt mount the system file (cache, efs etc...). I tried a nand erase + repartition but odin fails them too. i dont think that the nand is broken, just something doesnt allow me to access
what should i do?
Try this
Have u tried mounting external usb stick with otg cable? what version of odin re u using?
Alternatively try installing custom recovery like philz and then try flashing a rom.
let me know if that helps.
Hey, i have the same problem.
i took my phone out of my pocket and it was turned off. I tried to boot it but it got stuck at Galaxy Note II logo.
When i opened recovery (i use teamwin) , it shows in the log similar error messages to yours. It won't mount any of the partitions. I also tried repartition with odin, but it fails too.
I think the internal storage (the emmc) is broken in our phones and we can't really do anything about it. But i'm not sure.
Today my N7100 suddenly rebooted without any warning and got stuck at initial Samsung boot logo (even sound gets into loop). I managed to enter recovery and tried to wipe cache partition. But every time I try to wipe anything or delete via twrp file manager - phone reboots
Should I try re-partitioning via Odin? What pit file do I use?
lorendroll said:
Today my N7100 suddenly rebooted without any warning and got stuck at initial Samsung boot logo (even sound gets into loop). I managed to enter recovery and tried to wipe cache partition. But every time I try to wipe anything or delete via twrp file manager - phone reboots
Should I try re-partitioning via Odin? What pit file do I use?
Click to expand...
Click to collapse
you can try to use Odin, but probably you have faulty eMMC, many similiar cases around the forums about rebooting and stuck on Samsung logo.
Probably PC won't recognise your phone and there will be nothing else to do, but to give it to service
Miracles happens! Re-partitioned and fully erased nand via Odin and managed to upload the rom! Have tried 3 time before it succeed (crashed few time on system and cache image writing). Everything seems fine so far. Won't upgrade the rom from the stock 4.1.2 for a while to keep phone working. I have the insane emmc chip by the way. Hope it won't fail again.
Hi Guys! I have a problem, and i really don't know how can i fix it.
My phone boots normally, but when boot finish this error appear in the screen:
«Encryption was interrupted and can't be completed. Phone data cannot be used anymore.
To continue using your phone, you must restore factory settings. After the restoration, you can restore data backed up in your Google Account to your phone»
There is a "Reset Phone" button but if i push it nothing happen.
I have tried to clear data/cache in recovery but nothing changed, I have tried to install a new ROM (i tried a lot of ROMS) but when it arrive to 50% more or less installation fails.
I have tried this guide oppoforums.com/threads/guide-how-to-recover-your-bricked-find-7-7a.23067/ but it cannot work (Image Attachment)
Also FASTBOOT can't work. (For exemple: if i try to flash recovery it fails remote: failed to flash recovery / erase userdata / cache)
I really don't know where can i also looking
Help me please!
Anyone?
I'm having the same problem....
Restoring an old backup woth TWRP results in the same error.....
hi guys this happened to me too,
luckily I had twrp 2.8.6.0 flashed for recovery.
think you should still be able to get into fastboot if you do a battery pull
then poweron with the powerbutton and volume up till you see the oppo man icon.
then you should be able to flash your recovery with the latest twrp.
if you seen the penquin then this may not work for you. As i have not done a hard recovery before so i dont know if it would work.
I saw the oppo man so i was able to fix it by:
booting into twrp recovery,
i selected wipe --> advanced and there was an additional option to do a wipe for encrypted volumes and i selected all partitions to be wiped
then i installed i had downloaded on my SD card, it was ColorOS 2.0.8i i believed and it fixed it.
sorry if i am a bit grey about the details i did it a while ago so.
Actually found this in the cm12.1 nighlies thread
http://forum.xda-developers.com/showpost.php?p=58304054&postcount=14
issue is possibly due to unified partitions
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