Hi there,
Is there any other method to access fastboot mode rather than pressing the camera botton n the power botten together??? coz i have not being able to access the fastboot mod by doing so...dell logo appears and says factory reset and reboots. Please help!!!!!
Have you been trying to install a rom on your phone then? I had a situation today going from MIUI back to O2 stock froyo rom, which always gives me grief. In the end, when the phone gets really messed up the best way back is to use the recovery tool (qdl tool), but this is one to use with caution. If your not sure what your doing, spend a bit if time reading posts here to make sure you get all the drivers installed correctly.
To my knowledge there is no other way to get fastboot working besides the camera key.
Sent from my Dell Streak using xda premium
Hey,
thanks for your suggestion, after this prob i have been trying to use qdl tool
but not being able to install the driver, please can u post the steps to install the driver. it would be hearty appreciated.
Win7 32 bit.
themask123 said:
Hey,
thanks for your suggestion, after this prob i have been trying to use qdl tool
but not being able to install the driver, please can u post the steps to install the driver. it would be hearty appreciated.
Win7 32 bit.
Click to expand...
Click to collapse
Here are some links I found helpful:
http://forum.pocketables.net/showpost.php?p=59264&postcount=2
I have also spotted this - which tells you how to install the qualcom drivers which QDL needs. You also need to install the ADB driver from Dell which you can download from here:
http://www.dell.com/support/drivers...ileFormats?DriverId=R291096&FileId=2731115717
And I have used this to get my streak back when repairtool failed:
http://forum.xda-developers.com/showpost.php?p=19544875&postcount=3
That will probably get you to fastboot again, from there you can use StreakMod to mount the sd card, copy the Update.pkg of choice ( I did O2's 319 Froyo) and then reboot into fastboot, flash the matching recovery to the update.pkg, then do the vol+ and vol- boot and choose option 2 - software update option. Then, if all is well, the rom will install then the installer does the low level install stuff and hey presto - one working streak!
Good luck with all this. Oh, and here is a link that is a complete life saver when your looking for all this stuff
http://mirror2.streakdroid.com/manii/
It has it all. Check out http://mirror2.streakdroid.com/manii/Tools/ which has the repairtool and streakflash zip's. Manii is a complete life saver for sure! There are all the ROM's and matching recoveries in here too - so its a one stop shop.
I hope you get it back. One thing I've found out the very scary way is that the streak is one tough device to brick - there always seems to be a way to get back - unless you do the fastboot wipe option - then it's game over. I hope you have not done that!!
Good luck!
try using driver from this link https://www.google.com.ph/url?sa=t&...wMsgpQ_PiAP-8KRWw&sig2=RYdtwQOsIk10srEObUdY7g
extract the rar file and navigate it once you are upgrading driver. you should see "qualcomm cdma technologies msm" under other devices on your device manager (assuming you are using win7 32bit)
here is the process.
1. device is off. press the volume up button and connect to the computer.
2. go to device manager look for other devices and see if there is qualcomm cdma technologies msm you should have to update it using the driver mentioned above.
3. once the driver were successfully installed you can now use the qdl tool.
chriscullen42 said:
Here are some links I found helpful:
http://forum.pocketables.net/showpost.php?p=59264&postcount=2
I have also spotted this - which tells you how to install the qualcom drivers which QDL needs. You also need to install the ADB driver from Dell which you can download from here:
http://www.dell.com/support/drivers...ileFormats?DriverId=R291096&FileId=2731115717
And I have used this to get my streak back when repairtool failed:
http://forum.xda-developers.com/showpost.php?p=19544875&postcount=3
That will probably get you to fastboot again, from there you can use StreakMod to mount the sd card, copy the Update.pkg of choice ( I did O2's 319 Froyo) and then reboot into fastboot, flash the matching recovery to the update.pkg, then do the vol+ and vol- boot and choose option 2 - software update option. Then, if all is well, the rom will install then the installer does the low level install stuff and hey presto - one working streak!
Good luck with all this. Oh, and here is a link that is a complete life saver when your looking for all this stuff
http://mirror2.streakdroid.com/manii/
It has it all. Check out http://mirror2.streakdroid.com/manii/Tools/ which has the repairtool and streakflash zip's. Manii is a complete life saver for sure! There are all the ROM's and matching recoveries in here too - so its a one stop shop.
I hope you get it back. One thing I've found out the very scary way is that the streak is one tough device to brick - there always seems to be a way to get back - unless you do the fastboot wipe option - then it's game over. I hope you have not done that!!
Good luck!
Click to expand...
Click to collapse
Thanks a lot my streak is up and running
Whoo Hoo! Great news! I am so please for you
I know the feeling of relief when it all starts to get back to normal again - I have ended up back on Dell's latest 2.2 rom (360) and it's been rock solid ever since. I have not found any rom to be better or more reliable.
angelerikz said:
try using driver from this link https://www.google.com.ph/url?sa=t&...wMsgpQ_PiAP-8KRWw&sig2=RYdtwQOsIk10srEObUdY7g
extract the rar file and navigate it once you are upgrading driver. you should see "qualcomm cdma technologies msm" under other devices on your device manager (assuming you are using win7 32bit)
here is the process.
1. device is off. press the volume up button and connect to the computer.
2. go to device manager look for other devices and see if there is qualcomm cdma technologies msm you should have to update it using the driver mentioned above.
3. once the driver were successfully installed you can now use the qdl tool.
Click to expand...
Click to collapse
You saved me !!! :good: Thank YOU!
themask123 said:
Hi there,
Is there any other method to access fastboot mode rather than pressing the camera botton n the power botten together??? coz i have not being able to access the fastboot mod by doing so...dell logo appears and says factory reset and reboots. Please help!!!!!
Click to expand...
Click to collapse
just one solution, streakflash. search this forum for streakflash.zip, and you must find the driver for safe mode option to your pc. the driver is from samsung. after you done connecting your DS to PC, run qdl tool, after done, fastboot mode, reflash, then recovery mode to reinstall rom.
what if?
chriscullen42 said:
Here are some links I found helpful:
http://forum.pocketables.net/showpost.php?p=59264&postcount=2
I have also spotted this - which tells you how to install the qualcom drivers which QDL needs. You also need to install the ADB driver from Dell which you can download from here:
http://www.dell.com/support/drivers...ileFormats?DriverId=R291096&FileId=2731115717
And I have used this to get my streak back when repairtool failed:
http://forum.xda-developers.com/showpost.php?p=19544875&postcount=3
That will probably get you to fastboot again, from there you can use StreakMod to mount the sd card, copy the Update.pkg of choice ( I did O2's 319 Froyo) and then reboot into fastboot, flash the matching recovery to the update.pkg, then do the vol+ and vol- boot and choose option 2 - software update option. Then, if all is well, the rom will install then the installer does the low level install stuff and hey presto - one working streak!
Good luck with all this. Oh, and here is a link that is a complete life saver when your looking for all this stuff
http://mirror2.streakdroid.com/manii/
It has it all. Check out http://mirror2.streakdroid.com/manii/Tools/ which has the repairtool and streakflash zip's. Manii is a complete life saver for sure! There are all the ROM's and matching recoveries in here too - so its a one stop shop.
I hope you get it back. One thing I've found out the very scary way is that the streak is one tough device to brick - there always seems to be a way to get back - unless you do the fastboot wipe option - then it's game over. I hope you have not done that!!
Good luck!
Click to expand...
Click to collapse
what happen if there is no fastboot on your phone...is there a way to put it back on?
Related
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!
i cant boot my huawei u8180 into recovery
i rooted it by super one click
when i tried to flash recovery with rom manager premium it restarts then freeze in boot screen
tried to reset my phone from settings ,privacy it also reboot but freeze on boot
i dont know wt to do
PLZ HELP ME WITH THIS ISSUE
plz any one tell me anything i can do with this problem
i cant even reset my phone
plz reply
thanks guys , i solved my problem alone ,, and insalled cyanogenmod 7.2
everything is ok now
how do you solved your problem with huawei u8180? i have the same isue.
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Norpan70 said:
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Click to expand...
Click to collapse
So you could only boot into CWM by pressing power+volume+search? The regular way (power+volume) would lock up like it does to me, is that it?
Anyway I tried your key combination and it still freezes...
Codeman666 said:
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Click to expand...
Click to collapse
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Maeur1 said:
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Click to expand...
Click to collapse
I already flashed about 5 times and still freezes
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
bk109 said:
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
Click to expand...
Click to collapse
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Codeman666 said:
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Click to expand...
Click to collapse
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
bk109 said:
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
Click to expand...
Click to collapse
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Codeman666 said:
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Click to expand...
Click to collapse
Nothing specific -you just have to reboot in fastboot mode (just restart the phone while pressing Power and Volume Down. Windows should chirp and install the drivers automagically - afterwards just use that command discussed earlier and it should flash your recovery without any additional prompts (it should only print out a confirmation of a successful flash) and you should have the CWM ready to go
Edit: I put my device into fastboot mode on a clean Windows install (a Win8 Consumer Preview) and it did autodetect and install the relevant driver without restarting itself
No luck... Now it's driver issues
When booting the phone with either the vol up or down pressed and pluging in the USB my PC isn't recognizing the driver, I used both drivers you sent me.
Initially it's detected as Android 1.0 device, upon fetching the drivers it gets named "Android Sooner Single ADB Interface".
As I refresh device manager it goes back to Android 1.0 with an exclamation mark.
I think it's a driver signature issue, I'll try again in a couple of hours in a different PC
edit:in debug mode I have no driver issues and I can even detect my phone with ADB
Finally!
Tried it in another computer, auto downloaded some ASUS adb driver and installed fine.
Flashed latest CWM recovery with fastboot and now I'm able to boot into CWM!
Thank you so much for your help!
Sry for bumping.
So, i had the same trouble with the drivers. But i just downloaded HiSuite directly from the Huawei Site and these fix my problem with drivers to use adb without troubles . Hope this help someone.
BTW, Thanks bk109!
It did helped me thx man
Sent from my U8180 using xda app-developers app
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
I would like to know if someone could make a custom recovery and a stock version of android that I could put on my Blu Pure XR. I don't care if get rid of the 3d Touch on the phone. I just would like to have the stock android interface again and probably also the ram management will be better on the stock version.
I have the same request, would love to see TWRP. I'd like to install pixel launcher as system app and remove the adsup fota spyware.
The Pure XR is otherwise a great phone. Power management on stock is fantastic, i can get 6-7 hours of screen on time.
The Pure XR is essentially a Gionee S8 but sadly I dont see any custom recovery or development interest for that either.
Include me as well. Thanks
So the Pure XR is similar/same to the Symphony Helio S20...
There's a thread here that has a working twrp: https://forum.xda-developers.com/android/general/how-to-root-symphony-helio-s20-t3491123
I tested the recovery.img by loading it with fastboot without flashing and it worked!
You'll need adb/fastboot and the drivers first. Then boot the phone into fastboot mode by holding power + Up keys.
Select fastboot. After that, run: fasboot devices to make sure your phone is detected. Once detected:
fastboot oem unlock
reboot the phone, it'll do a force wipe
hold power+up keys again and boot to fastboot mode
Now, run this on your PC: fastboot boot recovery.img
Once the image is transferred, the screen goes blank...wait a min or two and TWRP will show up.
rom/firmware blu pure xr?
Anyone found a good stock ROM/Firmware for the Blu Pure XR?
if you finde one just tell us
ishman27 said:
Anyone found a good stock ROM/Firmware for the Blu Pure XR?
Click to expand...
Click to collapse
if you finde one just tell us
exciter0 said:
So the Pure XR is similar/same to the Symphony Helio S20...
There's a thread here that has a working twrp: https://forum.xda-developers.com/android/general/how-to-root-symphony-helio-s20-t3491123
I tested the recovery.img by loading it with fastboot without flashing and it worked!
You'll need adb/fastboot and the drivers first. Then boot the phone into fastboot mode by holding power + Up keys.
Select fastboot. After that, run: fasboot devices to make sure your phone is detected. Once detected:
fastboot oem unlock
reboot the phone, it'll do a force wipe
hold power+up keys again and boot to fastboot mode
Now, run this on your PC: fastboot boot recovery.img
Once the image is transferred, the screen goes blank...wait a min or two and TWRP will show up.
Click to expand...
Click to collapse
When I connect the phone through Fastboot and enter the command "fastboot devices," the phone is never recognized. I'm using Windows 10. Any help would be appreciated.
I used Linux instead. Have you installed the mtk and adb windows drivers?
exciter0 said:
I used Linux instead. Have you installed the mtk and adb windows drivers?
Click to expand...
Click to collapse
Yes, I installed the mtk and adb drivers however while adb works and detects my phone, fastboot does not.
Ok, I attempted using the SP Flash Tool on Windows 10 and successfully installed TWRP and rooted the phone. The only flaws are that the phone takes a few minutes to load into TWRP and unfortunately, there are still no custom roms on the device. It is a good start however.
Galaxxus_Rosarrius said:
Ok, I attempted using the SP Flash Tool on Windows 10 and successfully installed TWRP and rooted the phone. The only flaws are that the phone takes a few minutes to load into TWRP and unfortunately, there are still no custom roms on the device. It is a good start however.
Click to expand...
Click to collapse
Hey bud, big favor, would you describe step by step the rooting process, I used SP Flash Tool on windows 7 to install TWRP and it gave the ok check marK, then I tried to boot into recovery and I found out that TWRP was not installed. Do you have to unlock the bootloader to be able to install TWRP using SP Flash Tool? Thanks in advance.
Sent from my SM-G935T using XDA-Developers Legacy app
Hello everyone, I need your help, I've been trying to unlock my bootloader to root my phone, under setings I have developer options-OEM UNLOCK, but I only get as far as FASTBOOT MODE using my laptop as well as my pc, I tried this process with Windows 10, Windows 7 and latest Ubuntu. I tried different data cables, different usb ports 2.0 and 3.0 and nothing seems to work, I can put the phone on FASTBOOT MODE with my pc or lap, but then after that it looks to me that there is no comunication between my pc and phone. I installed all drivers several times and under DEVICE MANAGER everything looks good, as far as data cables I'm using 2 blu original data cables as well as aftermarket ones. Any help will be appreciated. Thanks in advance and have a good day.
Sent from my SM-G900T using XDA-Developers Legacy app
oscarmaldonado said:
Hey bud, big favor, would you describe step by step the rooting process, I used SP Flash Tool on windows 7 to install TWRP and it gave the ok check marK, then I tried to boot into recovery and I found out that TWRP was not installed. Do you have to unlock the bootloader to be able to install TWRP using SP Flash Tool? Thanks in advance.
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I remember something similar to this happening to me when I used a different version of SP Flash tool. Try SP Flash Tool v5.1624.00.000. After this make sure you have the scatter file for the MT6755 as well as the recovery file for the phone. Make sure that you have selected the scatter file for the phone and that the recovery.img is in the same directory as the scatter file.
Once this is done, make sure that you have installed the preloader or VCOM driver for the phone. This is tricky as the opportunity to apply the correct driver comes when you are powering on the phone and in this time you must click on the device that pops up in this time, right click it, and click properties.
Once this is done, go back to SP Flash Tool and click download, your phone must be off and unplugged before doing this. Then after this step, plug in your phone and the download process should begin (this might take a while). After this, boot into recovery mode which also will take around 3-5 minutes maybe more. After this you will have TWRP installed and from there you can install various apps including SU.
Galaxxus_Rosarrius said:
I remember something similar to this happening to me when I used a different version of SP Flash tool. Try SP Flash Tool v5.1624.00.000. After this make sure you have the scatter file for the MT6755 as well as the recovery file for the phone. Make sure that you have selected the scatter file for the phone and that the recovery.img is in the same directory as the scatter file.
Once this is done, make sure that you have installed the preloader or VCOM driver for the phone. This is tricky as the opportunity to apply the correct driver comes when you are powering on the phone and in this time you must click on the device that pops up in this time, right click it, and click properties.
Once this is done, go back to SP Flash Tool and click download, your phone must be off and unplugged before doing this. Then after this step, plug in your phone and the download process should begin (this might take a while). After this, boot into recovery mode which also will take around 3-5 minutes maybe more. After this you will have TWRP installed and from there you can install various apps including SU.
Click to expand...
Click to collapse
Thank you very much, I'm gonna give it a try as soon as I get a chance, I'll report back. Thanks again.
Sent from my SM-N910T3 using XDA-Developers Legacy app
Hi everyone, TWRP has been released by lopestom here https://forum.xda-developers.com/pure-xr/development/twrp-twrp-3-1-x-x-blu-pure-xr-p0030-t3623865
Since the Pure XR threads are very slim here I thought I'd post this here.
Seems my XR's data has got very slow, signal strength weak, etc.
Trying to figure out if this is Cricket or something up with the phone. My wife has a Blu Life one X3 and the same Cricket and her signal and data speeds are always better than mine.
What are some things to check/look for? I've tried a few like manually choosing the Network, changing the APN settings, etc.
Any further advice would be greatly appreciated.
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
All you will need link, at the end of the post. I don't know for how long it will be up, but you can use it for now.
By the way.... Should you find something useful here... please hit the thanks button in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00 (or any latest version).
Steps:
1. Install the windows drivers you downloaded
Note : If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
2. Open the folder you extracted SP Flashtool and run it as administrator.
3. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet. (should work with holding the power key down for a little longer than 10 seconds. If not hold down volume key and power button for the same amount of time - tested and working)
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a. adb reboot bootloader
b. fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10. Choose reboot to system and allow complete boot cycle! Essential!
11. Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version).
12. Once installed back to the windows terminal and issue:
a. adb reboot bootloader
b. fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note : Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
All you will need and credits:
https://drive.google.com/drive/fold...ourcekey=0-SDvJaXtWWk-TY9B53ct8dw&usp=sharing (thanks button, thanks button, thanks button!!! )
Results:
(it is in Greek, but you get the idea )
Hope I have helped! Happy playing with the commands and whole process! :good:
Lastly, if you get stuck at any point, you can either use this thread or PM me for further advice, explanation and/or any kind of assistance.
Note: Special thanks to @MotoJunkie01 for actually taking the time to further help people on this thread, as unfortunately I do not currently have the time to do so myself. It is worth checking out @MotoJunkie01 's threads also. There, you can find very useful and updated information.
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
If you find it useful, just hit thanks in the end
A. Unbrick
This requires flashing a clean stock rom. You will need:
a. stock rom for the TB3-850F (Google is you friend )
b. Sp Flashtool (you can download from their official site). From there, also download the MediaTek USB VCOM drivers and Driver Auto Installer v1.1236.00
Steps:
1. Install the windows drivers you downloaded
2. Open the folder you extracted SP Flashtool and run it as administrator.
4. Unzip the rom file you downloaded.
4. Inside the folder of your unzipped rom file, look for a file similar to XXXXXXXXXX_scatter_file.txt
5. Load this in the SP Flashtool (click downlad tab, then scatter loading, load this file in there. It should load your rom you will see some colours, etc...
The tricky part:
Assuming you have correctly installed the drivers:
1. turn off the device (well if bricked it is turned off all ready) just make sure, and in SP Flashtool click options and 'with battery'.
2. Click the green download button on SP Flashtool.
3. Hold down the Vol down key on your device and connect it to a usb port.
4. If you see a red line and continue to yellow, all is probably good! Don't let go of the vol - button until yellow line reaches 100%
B. Root and TWRP recovery
This requires that you have or download:
a. platform tools (adb and fastboot)
b. a twrp.img (image file) for the lenovo TB3-850F copied to external SD Card and platform tools folder (google is... useful )
c. latest supersu.zip (flashable) copied to an external SD CARD
d. busybox.apk
Steps:
1. Grab tablet, go to settings ---> about tablet ---> click version number 7 times to enable developer options
2. From settings again click developer options and enable OEM Unlocking and usb debugging
3. Navigate in the platform tools folder. While holding SHIFT right click and select open commandline here (or similar)
4. Connect tablet to PC and in the command line issue: adb devices
If a weird number shows up and says device on the left you are all good to continue.
5. Now on the command prompt again issue: adb reboot bootloader
Your tablet should now reboot to fastboot (big Android, laying down)
6. Issue command: fastboot oem unlock (also check tablet screen for confirmation)
Wait a little bit and reboot your tablet.
**At this point it is ESSENTIAL to leave the tablet to fully boot. The bootloader unlock triggers a FACTORY RESET which you must leave to complete and set up your tablet from the beginning.
** It is also ESSENTIAL to complete the boot and set up cycle because, after the automatic factory reset you will need to RE-ENABLE developer options and usb debugging. Once you are done continue to 7.
7. In the platform tools folder copy the twrp.img (you should have downloaded earlier, check upwards... )
8. Open the command line again and type:
a.adb reboot bootloader
b.fastboot boot twrp.img
** This will load up TWRP recovery only for this boot time.
****BE EXTRA CAUTIUS TO -NOT- ALLOW twrp to make modifications. Essential! Should you do otherwise go back to how to unbrick your tablet.
9. Choose install, and install supersu.zip.
10.Choose reboot to system and allow complete boot cycle! Essential!
11.Your tablet should now be rooted. However to succesfully flash the twrp recovery you need to have Busybox installed. Download as .apk and install it (at the time of writing this I believe Busybox 54 is the latest version.
12.Once installed back to the windows terminal and issue:
a.adb reboot bootloader
b.fastboot boot twrp.img
ONCE AGAIN - DO -NOT- ALLOW twrp to make modifications!!!!!
13. From you external SD Card install twrp.img, select recovery when prompted.
14. Reboot to system and enjoy!!!!
Note 1: Install an app that makes it easy to boot to recovery. (I personally use root essentials - Trying the combination keys did nothing for me, or just poped up the chinese options menu. That does not mean the recovery has not been installed correctly. Booting to recovery from rootessential menu, boots straight to twrp)
Note 2: If you encounter problems installing Windows drivers in Windows 10, google how to install unsigned drivers in Win10
I apologize for not being able to post links, but I believe the required software is not particularly hard to find.
Hope I have helped! Happy playing with the commands and whole process! I will continue to help as much as I can :good:
Click to expand...
Click to collapse
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
MotoJunkie01 said:
Good guide. This tablet has temperamental steps involved with custom recovery and root. This guide gives a good outline of those steps. Here is a link to my thread for Stock Android 6.0 firmware for this tablet for members who need a stock ROM.
https://forum.xda-developers.com/android/general/rom-lenovo-tab-3-8-tb3-850f-android-6-0-t3593043
---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------
Sorry, didn't mean to quote the entire OP....
Click to expand...
Click to collapse
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
r&xp said:
Thank you, I appreciate your comment. I was really enthusiastic to read that you are working on a pure Stock Android 6.0 ROM for this device! Will definitely be waiting for that!
Thank you again!
Click to expand...
Click to collapse
Thank you for the encouragement. I am in hopes that we can eventually get a dedicated device forum for the tb3-850f. I truly believe this tablet has the potential for plenty of future development.
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Rimmir said:
@r&xp I love you so much, I was in the same predicament as you and you helped get my tablet running again. Just wanted to mention, I had to hold volume down when plugging in the USB for the SPFT step instead of volume up. THANK YOU AGAAAAAAAAAAIN <3
Click to expand...
Click to collapse
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
r&xp said:
Thanks for the comment!!! :silly:
Glad it worked for you. Isn' t it like a really good feeling when you actually see your bricked device boot correctly for the first time after you had almost deemed it unusable???
(also... a... small request... could you please click on that thingy... you know... that ehhh... thanks button??? :angel::angel:)
Click to expand...
Click to collapse
Lol yessir, thanked!
MotoJunkie01 said:
Just an update, since damaging my TB3-850F, I have since ordered another unit from Office Depot which is due to be delivered Monday or Tuesday. Once it arrives, I'll finish my TWRP flashable stock 6.0 ROM for this device and start back on the modified stock ROM.
Click to expand...
Click to collapse
Looking forward to it. I picked mine up from walmart just yesterday for using as a google maps/car media center
My Lenovo Tab 3 replacement finally arrived in the mail. I'll be picking up where I left off on compiling both unmodified stock and custom stock-based ROMs for this tablet.
On my modified stock based ROM, I'm considering the implementation of Substratum (Root Ver) for theming, but I would like to get the input of other device owners first. So far, I have debloated, deodexed and zipaligned the OS. I am including the modified/patched boot image with SuperSU v2.79 SR3 binaries installed for systemless root, Nova Launcher, Pixel Icon Pack, BusyBox v1.26.2 binaries pre-injected in /su/xbin/, and Kernel Adiutor-Mod installed in /system/apps/ for user defined adjustments to the stock kernel and governors.
You guys please give me input on what you would like included in the ROM. Thanks
r&xp said:
Hi all!!
This is for all the people who managed to softbrick (or hardbrick) their Lenovo Tab 3 8' (TB3-850F) tablets!
Click to expand...
Click to collapse
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
chienfou said:
I had a Lenovo Tab3 that bricked during the initial set up and this saved me for having an expensive paperweight! The process worked like a charm. You ROCK!
Click to expand...
Click to collapse
Really glad it worked for you!!!
Thumbs up! :good::good:
load the scatter file .txt in SP Flashrom is OK ... it show me purple color until finish loading the file.
but how come when I hit the green button Download, it seems like nothing downloading,
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
yiukiang said:
thanks God, and thank you so muchhh muchhh muchhh for saving my tablet... after 2 days struggling with this brick
thank you the topic thread and MotoJunkie01 led me here :crying::fingers-crossed:
Click to expand...
Click to collapse
Try again to get TWRP installed to your /recovery partition or, alternatively, try to simply boot into TWRP from fastboot with the fastboot boot twrp.img command. It is common for members to experience some difficulty in installing custom recovery on this device. It has been my experience that most members are successful the second time around.
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
yiukiang said:
Thanks MotorJunkie!! But mine after was saved from brick from this thread, i was rooted it also by your instructions from other thread.. Now the gps from GoogleMap doesn't determine the location (even the location already turned on ) ... Plus i couldn't check the systemupdate ( it says connection network failed even i was connecting to wifi already) ...
What should i do, or do you know how to fix it?
Click to expand...
Click to collapse
System updates (OTAs) won't install on rooted operating systems. To install an OTA, you must have unmodified stock /boot, /system, and /recovery partitions installed. On the GPS issue, go to Settings, Apps, and ensure Google Maps has been granted location access permission.
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
xavier234 said:
Hi ...
I followed this guide but during the unbricking' I unplugged the device from USB (since I could not see any input on device or indication in SP Flash Tool).
Now the device will not turn on at all (previously I would see the Lenovo Logo splash screen but then it would just stay at this screen. Now i do not see anything).
When I plug into computer by USB, it causes my computer to freeze up (Windows 10).
Any ideas or is this now completely bricked? (hard bricked).
Click to expand...
Click to collapse
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
MotoJunkie01 said:
It sounds like a hard brick. I can't speak for the OP, @r&xp on this, so you may want to get his advice. Have you tried the OP's methods of using your hardware buttons for forcing the device into adb/fastboot recognition? I think this is your only chance of recovering it. By it not powering on, from my experience, a bootloader or bootloader dependent partition has been corrupted, thus hard bricking the tablet.
Click to expand...
Click to collapse
Hello, I'll weigh in on this one. There are multiple threads above the TB3-850F on this forum and also another forum.
I initially followed a different thread and instructions which caused my problem. Notably do not allow TWRP write access !!! This mistake caused the soft-brick.
Anyone following any other advice about TB3-850F or downloading any other image BEWARe. Only follow the advice in this thread by r&xp:
https://forum.xda-developers.com/android/help/lenovo-tab-3-8-tb3-850f-unbrick-root-t3598727
Following this advice I now restored original image and then rooted in just a few hours.. Thank you r&xp for the good advice. :laugh: