Related
Ok, i screwed up my Mini s. now i can only boot into the boot loader screen. and phone is CID locked so i can't run the r2sd command.
The question i have is this :
Can i still flash a custom rom or original rom while in bootloader mode ?
And if this is possible, can someone tell me how ?
Regards
Jacque
raymerjacque said:
Ok, i screwed up my Mini s. now i can only boot into the boot loader screen. and phone is CID locked so i can't run the r2sd command.
The question i have is this :
Can i still flash a custom rom or original rom while in bootloader mode ?
And if this is possible, can someone tell me how ?
Regards
Jacque
Click to expand...
Click to collapse
Yes you should be able to flash wizard love rom or the rom that your device was shipped with.
Just download either of these roms then put your device into bootloader mode. Make sure that the word USB is visible in the lower left corner of the bootloader screen when you plug in your usb cable. Then you just have to execute the installer of the rom that you downloaded.
If you get an error message you can use precautionary measures such as killing wcescomme.exe in task manager, turn firewall off, remove memory card, reboot pc etc.
Good Luck
Thnx for reply.
Eqx also just sent me mail and told me the same thing.
I am just busy charging the battery before i attempt another go at repairing the phone, i want to make sure that all goes smooth this time.
Will post my sucess or failure when i am done.
I need some serious help... I think I bricked my Nextbook Premium 7. I compiled a custom ROM and forgot to included a launcher. Didn't realize it until after I flashed it. My tablet is stuck in a bootloop and only way to shut it down is with the reset [pin hole] button. Power button does nothing except start it up. I have already tried to put the stock update.img on an external SD hoping it would boot from there, but it did not. I am not sure what to do next, I have looked all over google and xda. Please help!
Thank you in advance!
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
techno-update said:
Do you have a custom recovery installed? Did you try installing it threw fastboot files and cmd prompt on computer?
Please hit the thank you button if i helped!
Click to expand...
Click to collapse
There ins't a custom recovery installed, this device flashes by detecting an update.img and askes to install it. It doesn't get past what would be considered the kernel screen. This tablet doesn't work like a standard android phone. There are no hard buttons except the power button, so attempting to get into any recovery is not possible. It also doen't boot enough to add any files to it.
Sounds like your screwed. Sorry.....
Please hit the thank you button if i helped!
check out this link
http://forum.xda-developers.com/showthread.php?t=1410862&page=9
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Help !!
Please help, got the tablet yesterday NEXT7P12 YF091211085 by flashing the official site was a brick, the tablet will not turn on, the computer does not see it.
screen moved after installing rom
Hi, i don't know if I'm on the right place but if anyone can help me, please I haw the Nextbook 7 premium and have instaled costum rom on it, but after rebooting my screen position has moved from right to left 2 cm and from up to down 1 cm , so my screen is moved I don't know why I have try to install 3 other rom and factory firmware but the screen is still moved or should I say cut. Any ideas? please I have try to google it but no luck...
I no longer have my np7 but I did try just about every ROM for it. Never have I had or seen an issue like this, and in truth I can't think of what the issue may be.
There are different np7 variants and some don't play nice with custom ROMs (built sept 2012 and older lose WiFi) so you might have a model that can only use one software due to hardware/firmware change.
There never was much development for the np7 here, I think finlessbob and others are still working on it at freaktab.com maybe see if they can help
Sent from my Nexus 4 using xda premium
d33dvb said:
Ok, just bricked my Nextbook 7
Here is how I flashed a firmware without access to recovery:
If you are in a bootloop, Connect USB and Power.
Press and hold pin on back until you hear windows try to detect a device but the screen is off.
Download this: http://arctablet.com/assets/tools/Fi..._Tool_v1.4.zip
Install the driver from the drivers folder.
3. Installing the drivers on the computer
Following the tablet entering in recovery mode, the computer should now show it has found a new USB device and prompt for a device driver. Select the appropriate driver in the driver directory from the Rockchip Flash Tool 1.4 package.
It will then install the driver for RK29 Device
4. Sending the firmware to the tablet
The flashing tool should display a green square around the number 1 in the lower left area of the Windows application.
Select the firmware file to flash using the button in the top right area of the application. Select the update.img file from here:
http://www.multiupload.com/NQHSNZJSO2
Then push the Upgrade button to transfer the selected firmware to the tablet.
The firmware will be copied to the tablet, a progression counter will go from 0% to 100% on this step, followed by a verification.
You are done, let the tablet reboot and update itself. It should take a few minutes for the flash process to finish.
This procedure has been successfully tested on Windows XP 32 bits for flashing a bricked NextBook 7 Premium YF1011 (but should work on others)
Click to expand...
Click to collapse
Your link not working? Send alternative link please!
Hello Evrybody
i have a huge Problem with my ST15i
I had Rooted GB on it and evrything works fine till i decided to try a custom ROM
so i instal Recovery Tool and installed a Custom Rom for ST15 i
after installling and rebooting to the new rom, i noticed when i tried to open the screen lock bar that the touchscreen didnt react exactly - i had to slide at the other side of the display to unlock it!
So i decided to make the phone fresh with SEUS and ICS4.0! After SEUS update i restarted my phone and the whole touch display didnt work anymore!
only the hardbuttons - i cannot back to any Recovery tool , with out touch display i cant switch to uUSB Debug Mode!!
Is there hope to help my Phone!!
Thx in Advatage!!
Hi,
This means you installed custom rom and it didn't work? And then you connected your phone to pc and used seus while you were on custom rom? You did not flash original sony from back first and updated (or tried to update) while you were on custom rom?
Have you tried to use flashtool? I don't know if your touchscreen has bricked up completely, but you could flash gb firmware back, so you have a clean gb rom.
For this download sony flashtool from here and install it. You go to the drivers section of the flashtool folder on your computer and install them. Then you download the 4.0.2.A.0.42 rom (for SK17i) rom from here and move it to the firmware folder of flashtool on your pc. Then you start flashtool and click on the flash. You select flashmode and then you select the 4.0.2.A.0.42 rom and click ok.
Then you turn off your phone (make sure it is over 50% charged) and hold volume down key. Then you plugin the usb cable to pc and smartphone while holding volume down. It should flash the original gingerbread rom.
If the flash finished you can hope that the touchscreen workd, if not I don't know a solution.
BUT: I DONT TAKE ANY RESPOSIBILITY FOR THIS METHOD!!!
If it has worked you can be lucky, if not you are on non-rooted gingerbread rom and could bring your device to the service, but I'm not sure!
OR: First read this thread cause he has similar problem!
Best regards
Michael
i managed it already to install androis SDK on pc and ADB Drivers - via Fastboot i can reach the Device and Bootloader seems to be open, the blue led is wworking, windows accepts my phone as installed android ADB Device - and when i try with Flashtool, and some other different tools to flash new kernel - i always become the mesagge ithe device must be rooted even from fastboot when i use the (fastboot flash boot boot.img) command
I will try some other things , when this does not helps so i try with service
THX
But led is working anyway, it doesn't say, that the bootloader is unlocked. Maybe really flash the 4.0.2.A.0.42 firmware using flashtool and then try if touch works, otherwise bring device to service, but I don't know if they can notice your try to install a custom rom.
Hope it will work for you!
Marethno said:
Hello Evrybody
i have a huge Problem with my ST15i
I had Rooted GB on it and evrything works fine till i decided to try a custom ROM
so i instal Recovery Tool and installed a Custom Rom for ST15 i
after installling and rebooting to the new rom, i noticed when i tried to open the screen lock bar that the touchscreen didnt react exactly - i had to slide at the other side of the display to unlock it!
So i decided to make the phone fresh with SEUS and ICS4.0! After SEUS update i restarted my phone and the whole touch display didnt work anymore!
only the hardbuttons - i cannot back to any Recovery tool , with out touch display i cant switch to uUSB Debug Mode!!
Is there hope to help my Phone!!
Thx in Advatage!!
Click to expand...
Click to collapse
to fix your problem:
flash stock firmware via flash tools
flash a custom kernel and flash that custom(that you had problem with)
flash stock firmware again
i had your problem and i fixed it.
so... 100%working
fixing
scorpion 13 said:
to fix your problem:
flash stock firmware via flash tools
flash a custom kernel and flash that custom(that you had problem with)
flash stock firmware again
i had your problem and i fixed it.
so... 100%working
Click to expand...
Click to collapse
what if on 4.0.4 rom so i need to reflash same custom firmware(problem)
Hey guys,
I am sorry if I am in the wrong place or am asking something wrong. This is my first time using these forums (and forums in general). If I need to be somewhere else kindly redirect me.
Anyway, I was with Verizon for a while but after some shady stuff I decided to break up with them. Beforehand I had bought outright a Sony Xperia Z2 Tablet. Because I did not want anything Verizon on it I decided to root it, and flash a good ROM onto it (Cyanogenmod was my idea, but at the time I don't think they supported it? I'm not good with ROMS). Anyway, the rooting was completely successful and I had a custom recovery (TWRP) installed. I was ready to flash the ROM. Unfortunately, I wasn't paying attention and grabbed the wrong ROM. What ended up happening is when I attempted to reboot after "flashing", the device didn't show anything on the screen and just kept vibrating. After some digging around I found it might be "soft-bricked". I had at one time found a guide that told me how to undo this by using SDK Tools and Fastboot Mode (blue LED), but cannot find the guide anymore.
I was wondering if ANYONE could help me undo this mistake, and get the tablet back to it's original state or with a nice compatible ROM. I am currently in Fastboot mode and it is plugged into my ASUS Laptop running Windows 7. Any and all help would be GREATLY appreciated. Thank you so much for taking time to read this.
EDIT: So a breakdown is I cannot interact with the tablet directly. There is absolutely no interface. Just a screen that won't turn on. Meaning if there is a method it can't be done on the tablet. The old guide I found was explaining how to do it through Windows while the tablet was plugged into it via USB.
Also the bootloader was never unlocked so I think that was also an issue.
First of all, if your bootloader is locked, you cannot install CM because you cannot change the Kernel. You can only use Sony-certified Kernels which won't work with CM. So Sony-based ROMs are your only options
But what you can do is:
- Go into fastboot mode (turn off your tablet, connect it to your PC and press volume up. If the blue LED shows up, you are in fastboot)
- With fastboot, you should be able to flash a ROM (preferably Android 4.4, so you can root again)
- Then root, install dual recovery
- Flash the correct ZIP
Alternative:
- Unlock Bootloader
- Flash recovery
- Flash CM
BabelHuber said:
First of all, if your bootloader is locked, you cannot install CM because you cannot change the Kernel. You can only use Sony-certified Kernels which won't work with CM. So Sony-based ROMs are your only options
But what you can do is:
- Go into fastboot mode (turn off your tablet, connect it to your PC and press volume up. If the blue LED shows up, you are in fastboot)
- With fastboot, you should be able to flash a ROM (preferably Android 4.4, so you can root again)
- Then root, install dual recovery
- Flash the correct ZIP
Alternative:
- Unlock Bootloader
- Flash recovery
- Flash CM
Click to expand...
Click to collapse
Can you simplify this? Where do I find the ROM (again, this was a tablet from Verizon so I assume on top of the Sony ROM I need the Verizon version of it?) And I understand I cannot install CM unless the bootloader is unlocked; do you know how to do this?
I'm confused by the first set of instructions as I cannot use the tablet directly. How will I flash the ROM (and which is the right ROM and where can I find it?) through the computer since the tablet can't be interacted with. There is absolutely no interface to interact with whatsoever. Which ROM do I download for the Verizon Sony Xperia Z2 Tablet and how do I flash it using Fastboot? I assume I do it thru my computer?
Sorry, but you'll have to Google a little bit - I haven't had your exact problem.
But as long as you can get into fastboot mode, nothing is lost.
There also is the Sony ftf tool or so, the Windows program name is Emma. This should be easier than using fastboot.
Also there is a sony site for bootloader unlocking. You can check whether your bootloader can be unlocked at all.
The story begins when I had twrp. i flashed the oneplus_x_oxygenos_3.1.1_community_build usb debugging turned on, and oem unlocking. I was successful, I had stock oxygen OS but I lost twrp in doing so.
retried to install twrp, it did not work, when i tried going to recovery it's stuck on oneplus logo. i tried to fix it with this , did't notice it was for Oneplus 2, so.... hard bricked my phone, i was able to recover with this but i could not install twrp. so i installed the stock recovery MM which works now. OS does not work anymore. for some reason when i try to flash the oxygenos_3.1.1 with stock recovery, it still fails. even when i tried installing a lower version rom.
Can anybody help me? this is my daily driver phone. currently using my nokia feature phone for calls and texts......
what I have:
Stock recovery
nandroid backup that i cannot use because i don't have twrp,
usb debugging turned off,
and oem unlocking off.
can access fastboot, sideload.
no access to OS.
Hatred for Pokemon Go
yay it's alive!!
this worked for me! http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
moderator kindly delete my post. Thanks!
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Exodusche said:
Don't know why people are still flashing community build with twrp. So much information on this. Yes we have a working twrp for 3.1.1 but that's for after its installed.
Click to expand...
Click to collapse
I guess some confusion might have been caused when it was posted on the OnePlus forums (and apparently a quote from a OnePlus rep) that the new build was "compatible" with TWRP. This was later clarified (by a poster, not OnePlus) to mean V41 of the blu-spark TWRP.
Chat with support confirms.
Kashaila said:
Sorry to keep you waiting. I apologize for the confusion. I have just confirmed from the specialist that TWRP is compatible with the new rollout.
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/...nity-beta-for-oneplus-x.464812/#post-15231909
Perhaps the mistake arises because it is not clear was that whilst TWRP is compatible, you couldn't actually flash the new community build with it! TWRP is only compatible (like you say) AFTER the flash!!
https://tapatalk.com/shareLink?url=...share_tid=3464987&share_fid=3793&share_type=t
[guide] unbrick device
This should help...
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
tjeus said:
Hi, i can' get the qualcomm driver installed. It says like the hash isn't in the catalog and that it is damaged or messed with.
The Driver Signature is turned off in W10, so do you know something?
Also there is no communication with fastboot, i can boot to it, to the fb logo on the opx, but no way to get contact.
Thanks
Click to expand...
Click to collapse
Change computer.
Try with an old windows 7.
Or, try this: http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Iirc, it's the same for Windows 10.
Sent from my ONE E1003 using Tapatalk
Himanshu Gusai said:
The solution for OPX hardbrick is similar to OPO and OP2 - you just need a Qualcomm driver and a recover package.
So,here we go !!
Step 1 :- DOWNLOADS :-
1.) Drivers :- https://www.androidfilehost.com/?fid=24052804347799753 (Extract these files to a folder on desktop.)
2.) Recovery Tool :- https://drive.google.com/folderview?...XM&usp=sharing (Download all files inside this folder and put them in a folder on desktop.)
Step 2 :- If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :- http://www.howtogeek.com/167723/how-...igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 sec and then power button. While keeping them pressed,connect OPX to PC.Hold volume up until your PC finds a new hardware .
Step 5 :- Go to device manager in your PC, find the new "QUALCOMM-HS USB Diagnostics xxxx" device or something like this (It must be Unknown Devices as QHUSB_BULK or under COMs and Ports as Qualcomm xxxx). Update its driver in property page using the Qualcomm driver provided (for 32bit windows, select x86 folder; for 64bit windows, select x64 folder).
Step 6 :- After installing the drivers,"Run As Administrator" the MSMDownloadToolV2.0 in the recovery tools folder.
Step 7 :- Click start at top left corner and wait for it to finish (Download Complete will come)
Step 8 :- Disconnect phone from PC and boot into system.
Now you can again do anything you wish to (unlock bootloader,etc).To unlock bootloader,go to developer options and tick "Enable OEM Unlock" first.
When you will need this guide ? :-
1.) If your phone is totally black (no racism)
2.) When you have locked the bootloader by mistake . (This happens when you flash a rom without having oem unlocking enabled.)
PS:- This method will wipe all data and restore your phone to OxygenOS and English Bootloader.
Thanks.
Click to expand...
Click to collapse
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache etc.
Then i went to flash sultan(with twrp, can't remember the version but i think it was new one), i had to change update script in .zip file to ONE before i could flash it.
Then when it flashed i tried to restart but it said no system.
I decided not to restart and flash OOS 3.1.3, it flashed and restarted...but it was constantly restarting, logo would show and 1 sec after it would restart, and it stuck in a loop. No recovery, no fastboot...
With a guide above i managed to get it to install recovery and rom, but when booting, after loading android apps, it would just say finishing boot and restart again...
So i had recovery and tried to flash a new recovery but bootloader is locked, and cannot be unlocked because, oem unlock is disabled....
I tried to flash OOS 3.1.3 with stock recovery but after clicking YES for flashing phone turned off. When i tried to turn it on it only shows logo, nothing booting....
And now when i try to use MSM Download tool everything is done but phone still doesn't boot anything at all......now it won't even get to the part with loading android apps.....
Can anyone help?? Could someone please upload recovery.img and system.img that i could put in MSM folder, maybe if it would flash that files it would work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Ovakisan said:
Hello, i have similar problem.
I tried to flash sultan rom on top of cm13 nightly, but before flashing i wiped everything, system,data, cache work?
Is there any other way to set oem unlock to enabled without developer options???
help help help
Click to expand...
Click to collapse
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Exodusche said:
The part when it said no system you would of been fine if you just let it boot. Did you wipe before flashing 3.1.3 after Sultan? You need to get old stock recovery to flash 3.1.3. Whether that be thru fastboot or using the unbrick guide.
Once you have booted 3.1.3 you can continue with fastboor flashing one of the updated twrp's (Sultans,blu sparksv41,Nachets.)
Click to expand...
Click to collapse
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Ovakisan said:
I did wipe yes, but within twrp not stock recovery, so that is what f**ed it up :/
Thru fastboot i can't do anything because bootloader is locked and cannot be unlocked. unbrick guide just boots, updates and starts android applications and then restarts.
A few minutes ago it managed to get into setup wizard, and i went skip skip skip just to get into settings and before i got in freaking thing restarted and now is again starting aplications in a loop......
Could i use different img files with MSM downloader? Where can i read more about msm downloader app and what it does?
Click to expand...
Click to collapse
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Exodusche said:
Can't you go through the steps to unlock bootloader now that you've done the hard brick guide? I'm not sure bro someone will help you.
Click to expand...
Click to collapse
The problem is that after going through guide, MSM downloader would say that its done, and it wouldn't boot in android, sou you can't get into developers options to enable OEM unlocking. And throught fastboot you can't do anything because its not enabled...
anyway if anyone is reading this that has same issue, just don't stop restarting, this little fu**** just managed to boot into android and i managed to get into dev options(after 3-4 restart, and 1 wipe cache data in stock recovery). after setting OEM unlock to enabled i tried to shut down phone through normal shutdown procedure but it got stuck, but force shut down with button worked and it saved OEM unlocking option on enabled. so i managed to unlock bootloader with fastboot.
So im with stock recovery now, lollipop ROM, should i try to flash OOS 3.1.3 now, or do i have to do something else prior to flashing????
I'm kind of scared now to do anything :'D
EDIT: ok, i ran into problem again -.-
twrp is flashed, latest. now when i try to flash cm13 or sultans cm13 i get this error.
http://imgur.com/a/BSpK1