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 have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Sorry to hear about your bricked phone. I can't help specifically as I don't have a Lenovo, but having a search around XDA there seems to have been some success reported in the following thread:
http://forum.xda-developers.com/showthread.php?t=2597590
See this post - http://forum.xda-developers.com/showpost.php?p=52013378&postcount=412
Another post in that thread suggests:
Turn off the phone --> Run minimal ABD and fastboot as admin--> just write the command for recovery install (don't hit enter yet)--> press volume + and volume - button and connect the phone to pc via usb--> now hit enter and voila. Your phone will boot in recovery.
Click to expand...
Click to collapse
Good luck!
anyone?
f4780y said:
Sorry to hear about your bricked phone. I can't help specifically as I don't have a Lenovo, but having a search around XDA there seems to have been some success reported in the following thread:
http://forum.xda-developers.com/showthread.php?t=2597590
See this post - http://forum.xda-developers.com/showpost.php?p=52013378&postcount=412
Another post in that thread suggests:
Good luck!
Click to expand...
Click to collapse
i tried this aldready, but my phone is locked bootloder so that method is no help. Thank you for your support anyway.
hientran41 said:
i tried this aldready, but my phone is locked bootloder so that method is no help. Thank you for your support anyway.
Click to expand...
Click to collapse
OK, but did you look at the second link there, to the specific post in that thread? It suggests a process for locked bootloader, which is why I thought it might help...
Anyhoo, I hope you manage to get it fixed somehow!
Is anybody have the droidboot.img file from the VibeZ K910 dualsim, pls upload it for me. i cannot find it anywhere.
I look into the second link as well. that method for user have a working phone but locked bootloader and want to downgrade.
Ah, OK. Sorry I couldn't help.
u fix your phone?
hientran41 said:
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Click to expand...
Click to collapse
hi do u fix your phone?
Geguniukas said:
hi do u fix your phone?
Click to expand...
Click to collapse
i bricked also
dunno what to do..
---------- Post added at 12:13 AM ---------- Previous post was at 12:13 AM ----------
hientran41 said:
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Click to expand...
Click to collapse
did you fixed the phone?
lenovo k910e 4.2.2 bricked after TWRP for 4.4.2 installation
Hi , this is my first time on the site , so forgive me if ive posted this in the wrong place.
I briked my Lenovo k910e running 4.2.2 rom with google apps purchased off Aliexpress.
What i did was run the flashrec.exe file for TWRP , but not until too late did i realise it was for 4.4.2 instead of 4.2.2.
Now i cannot boot the phone , TWRP was successfully installed and operational , but after about 20 reboots TWRP flash screen is stuck on the TeamWin logo and not accessable.
Ive tried mostl sugestions on this site and others without luck.
I can get the phone recognised with fastboot only after these commands ;
cd downloads
cd fastboot
adb devices
and it seems i may be able to push files to my device.
Is there a working link to the k910 OEM rom k910_ss_s_2_040_0109_131226 someone could direct me to.
All the links i have found so far are corrupted. Is there a way of repairing the TWRP recovery i have in the phone now.
Am I correct in assuming I have to install the OEM factory 4.2.2 ROM to wipe TWRP and istal Lenovo recovery ?.
Any help would be so appreciated. Thanks
Solution ( k910 bricked )
Ok here is the solution even if your device ( k910 dual sim ) is completely bricked as was mine.
I was stuck in Lenovo logo with no success in finding right and working drivers ( windows 7 64x ) and i was not able to to get in recovery official ...everything was just - somehow - deleted...
I had locked bootloader **** and was not be able to flash cmw in working mode ****
There was nothing for me that could recover my phone even if the "hard" way with QPST or miflash etc
So....after 3 days....find this solution and hope this will help you because it is soooooooooo easy finally!
Steps:
1) Download lenovo driver ( i think it is useless in fact but ok....just run it you dont have anything more to loose )
https://www.dropbox.com/s/frbpz16udrefoit/LenovoUsbDriver_autorun_1.0.112.exe?dl=0
2a) Download and install Minimal adb
https://www.dropbox.com/s/uvngsu4vz4hvsky/minimal_adb_fastboot_v1.1.3_setup.exe?dl=0
So now you have to use the right recovery image ( this file has to be inside minimal adb folder )....so here it is:
https://www.dropbox.com/s/ge05m1fe8n4qgb1/recovery.img?dl=0
2b)
Download this ROM ( this worked for me - with other i did try i did get an error )
http://www.needrom.com/download/lenovo-k910-vibeui-2-0/
prefer the last updated version ( 1501 )
Put this rom in the same ADB folder and renale zip in VIBE1411.ZIP ( in order to be easier later )
3) Turn off the device open Adb and write : fastboot boot recovery.img ( to have it ready )
4) Push volume + $ volume - at the same time and AFTER connect with usb to your pc - At the time the device will vibrate HIT ENTER in ADB
This will flash the recovery and after 1 minute device will open in a recovery screen with an adb update option ***
SELECT THIS adb update OPTION !
Your device kow it is ready to flash the new rom ! ( you will realize that everything is right from many usb beeps you will hear )
5)In adb console write : adb sideload VIBE1411.ZIP
This will take a little ....after that your device will reboot ! Dont panic if for a few minutes it will stuck in lenovo logo....
IT IS NORMAL AND YOU HAVE TO WAIT!
Hope this will help you.....please feel free to tell me if this worked for you.
C u
Same thing happens to my lenovo vibe z k910
buzzbuzz1 said:
Hi , this is my first time on the site , so forgive me if ive posted this in the wrong place.
I briked my Lenovo k910e running 4.2.2 rom with google apps purchased off Aliexpress.
What i did was run the flashrec.exe file for TWRP , but not until too late did i realise it was for 4.4.2 instead of 4.2.2.
Now i cannot boot the phone , TWRP was successfully installed and operational , but after about 20 reboots TWRP flash screen is stuck on the TeamWin logo and not accessable.
Ive tried mostl sugestions on this site and others without luck.
I can get the phone recognised with fastboot only after these commands ;
cd downloads
cd fastboot
adb devices
and it seems i may be able to push files to my device.
Is there a working link to the k910 OEM rom k910_ss_s_2_040_0109_131226 someone could direct me to.
All the links i have found so far are corrupted. Is there a way of repairing the TWRP recovery i have in the phone now.
Am I correct in assuming I have to install the OEM factory 4.2.2 ROM to wipe TWRP and istal Lenovo recovery ?.
Any help would be so appreciated. Thanks
Click to expand...
Click to collapse
After running twrp recovery it operates 3-4 times but now it flashes on twrp screen and screen goes blank and again flashes . I am unable to on it and as it shows only light and lenovo logo after that blank screen . Please help me in this. Its only detecting in adb recovery not any other mode.
lenove vibe Z k910 locked and stuck in logo
hello all
I ve done every word and many other tutorials but still the problem the same:
adb devices give just nothing
but fastboot devices gives the device
the driver is installed correctly detected in devices of the computer
here is the response for :fastboot boot recovery.img:
~/Desktop/lenovo]$ fastboot boot recovery.img (master✱)
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
FAILED (remote: Locked)
finished. total time: 0.538s
thanks for everyone to help
Boot into recovery under bricked condition
Today I bricked K910 after reinstalling GMS apk.
The phone hanged at boot logo.
Nothing can be from here.
I decided to take this risk.
I removed the back cover and disconnected the battery terminal.
After that I plugged back the terminal.
Several tries by power button and volume down to get into the recovery mode. All failed.
Each time it hanged at boot logo.
I have to redo the battery terminal unplug sequence again.
This is correct method to get into recovery mode.
Press power button and volume down till the Lenovo logo appears.
Move the power button finger to the position of the " Home " of the touchscreen position.
Hold till the recovery menu appears. Choose factory reset to erase the phone.
There was two lit small icon below. Make your choice.
The phone will be erased by reset.
Reboot after the process.
I solved my phone bricked problem.
Hope the method will solve your problem.
Good day to all K910 users.
my vibe z cannot access the recovery mode (PWR + VLM DOWN), it only vibrate. If turn on only stuck at Logo. Please help .
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:
So i wanted to flash a new firmware on my MTK Device (UleFone Power 2), but i ran into some Errors while doing so, thus , my phone died in the process.
Following Errors occurred, depending on which (SP Flash Tool;SPMultidownloadflashtool;etc) you use:
Errors:
Internal Buffer
STATUS_SEC_IMGHDR_TYPE_MISMATCH
Through digging and asking on the web, two wonderful and very very helpful people: alterogi and finally Sunray888
This solution popped up. Thank you so much to both of them!!
Solution:
But first: You are now warned, try this at your own risk.
Quoted from Sunray888, alterogi. Credits to them.
My German Guide (more detailed with Pictures): Outside of XDA
Side Note: For the UP2 Rom you use SPMultiPortFlashDownloadProject , for the UK6P ROm you use SPFlashTool.
(Links & Attachments below!) (Adb-Fastboot.zip & Checksum.zip)
Part1:
1. Download all the files. (Below are the links and attached files.
2. Extract each zip to its own folder. Then Put the files of the Checksum.zip into the ROM Folder of the Ulefone Power 2.
3. Run the Checksum.exe and wait until it is done. It will show up in the black CMD when it's finished. A new Checksum.ini should be in the folder now.
Part2:
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Get the Oukitel K6000 Plus ROm Version 2.0 Ready. Extract it to its own folder somewhere on your desktop.
3. Open the SPFlashtool and select the android scatter file of the Oukitel Rom.
4. Connect your phone, hold Volume down and press on "Download" in the SPFlashTool. Now you wait for the process to end, WHILE still holding the button down.
5. After it is done flashing your new Firmware unto your phone, start it like you would normally do. Disconnect your phone now. You can now also skip the Setup Details, since we still have to flash the original Firmware.
6. Go to Device Infos on the bottom of your phone settings, tap a few times on Build Number until the Developer Options activate. Go back and tap on Developer Options.
7. In here you activate OEM Unlock and USB Debugging. Back to the pc: Now you open a CMD Windows and navigate to your extracted ADB-Fastboot Folder. (Some Pictures of this are on my German Tutorial Thread, Link above).
8.Connect your phone, tick the avaible spot of the upcoming new popup notification. Shutdown your phone now. Hold Volume Up and Power Button at the SAME Time until the Fastboot Menu pops up.
Make sure your phone is still connected to the pc.
9. In the cmd window you will now have to type the following thing: fastboot oem unlock
9.5 Another Method to get into fastboot mode: (OR enabled usb debug, accept connection between your PC and Ulephone and send command fastboot reboot bootloader after that "fastboot oem unlock")
10. After the process is done. You are still in fastboot mode.
And let the phone connected to the Pc.
11. Now you have to flash the original ROM/Firmware. In this case only Version 17 will work.
On this step i had a lot issues with "insufficient buffer"-Errors under SP Flash tool, but there is a solution for this.
Be careful :
Try to use #SPMultiPortFlashDownloadProject Version 3.1620 - only this software worked for me,earlier Versions i tried ( v.3.1636 ) always showed an Error.
Current Status: Phone is still connected to pc, fastboot mode, oem has just been unlocked by yourself.
What to do now:
12 Open the SPMultiPortFlashDownloadProject, load scatter file of the Ulefone Power 2 Firmware, then press scan. Nothing will happen now, so be quick: Don't disconnect your phone.
Press Volume Up + Power Button at the same time to simulate a new connection to the pc. While the phone is still connected via cable! We have to do this. You will now hear a sound which you normally would here when connecting a new device to your Pc. Now you just have to keep holding the Volume Up Key.
IMPORTANT:
Don't let go of the button until the Programm shows up a Green Tick which signals the end of the Process. Now you can let go of the button.
13. After the scan has finished, press start and flash firmware. But how? It's easy. Just do the same again. ->>
13.1 Press Start in the Flash Programm.
13.2 We have to simulate a new connection. Hold Vol+ and Power Button. Until you hear the sound again, now only keep holding the Vol+ Button.
14. Wait for the green Tick Notification. Until then: Don't you dare let go of the Vol+ Button. When it shows up, you're pretty much done. Congrats!
15. Restore NVRAM and NVDATA.[/I] through mtk engineering mode: open dialer and call *#*#3646633#*#* , scroll down to GRPS and type in your IMEI (can be found in the box, in which your phone came shipped with). If it says something like that it's successfully written.-> Activate Airplanemode, wait a few seconds, deactivate it, activate Mobile Data Connection and wait. It should show a mobile data active.
Download Links: (I didn't upload those files,i simply shared the links, all credits to their respective owners. Use at your own risk.!)
UP2 Rom: Google Drive
Flashtool for UP2 Rom: One Drive
UK6P 2.0 + Flashtool: Click me
Checksum Gen Zip: --Below--
ADB Components: --Below--
UPDATING:
After flashing V15 Ulefone Firmware, use the SP FLASH TOOL to flash the newest firmware via "Firmware Upgrade" mode. remember to keep pushing vol up before connecting phone!
How to:
Press Download in Tool
Push and hold vol up
Connect cable to pc.
wait until green tick shows up.
Profit.
Same situation here. I've tried flashing with and without battery, no success. I can confirm that I did NOT lock the bootloader. Not that it helps me much.
I've tried using different versions of SPFT in addition to the multiport tool, but they either don't work with Power 2 scatter file, or show the same error.
This can potentially be a driver / USB issue, so I will probably try that next (different computer, fiddle with the drivers). I've also seen claims that SPFT v3 can happily flash over this, and then newer versions start working too, so try that if you can. It did not work for me - the download never starts on my computer with v3.
I can also add that I can flash preloader as well, although I try and leave that off when possible. The modem and lk* partitions show the same error you have, though, and the phone is dead.
I have managed to resolve this with a lot of help from Vivanyok on 4pda.
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Download Oukitel K6000 Plus ROM v2.0. Only this version will work.
3. Flash it. It will actually work just fine, no errors. I've used the latest SPFT.
4. Boot the phone into Android. In Developer Options, enable OEM Unlock.
5. Reboot into fastboot, do fastboot oem unlock.
6. After this, you can simply flash any Ulefone ROM for Power 2. Win!
7. Restore NVRAM and NVDATA.
Hope this helps somebody.
Thanks for your reply!! I will try that and report back ! I'm so glad there are people out here who help !
EDIT: OMG, You are my hero!!! The Flash Process went just fine, no errors. It boots up. Thank you so much! Now i can flash like a devil again, haha
EDIT2: So i could use the phone with the oukitel rom but i want the original rom, firmware.
So here is the other Problem. I can't flash them. I either get insufficient buffer error or the imghdr error.
Could you link me what you are using? I really need the phone. Thanks for your help in advance.! :S
Hi sm00th4f3
I add some advices to Vivanyok instruction by red letters --->
I have managed to resolve this with a lot of help from Vivanyok on 4pda.
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Download Oukitel K6000 Plus ROM v2.0. Only this version will work.
3. Flash it. It will actually work just fine, no errors. I've used the latest SPFT.
4. Boot the phone into Android. In Developer Options, enable OEM Unlock.
5. Reboot into fastboot, do fastboot oem unlock.
OR enabled usb debug, accept connection between your PC and Ulephone and send command
fastboot reboot bootloader
after that
fastboot oem unlock
6. After this, you can simply flash any Ulefone ROM for Power 2. Win!
on this step i had a lot issue with insuffitient buffer under SP Flash tool, but yesterday i win too.
be careful :
after oem unlocking you should NOT reboot ulephone to Android,let phone stay connected to PC
try use #SPMultiPortFlashDownloadProject version 3.1620 - only this soft help me,earlier i tried v.3.1636 but always error appear.
and when i started flashing i stayed ulephone connected to usb (i dont disconnect phone after oem unlocking) and i simulated connection by long press volume UP + Power buttons. You can control connection by default PC sound.
due in SPMultiPortFlashDownloadProject other interface i did not change flashing type, it was firware update by default.
After that my ulefone become alive.
7. Restore NVRAM and NVDATA.
good luck, if any questions ask me on 4pda.ru
So, i tried your nice guide, and it finally worked!! Side Note is: After fastboot oem unlock you have to scan with the #SPMultiPortFlashDownloadProject version 3.1620 your phone first, and then like you have already said, use the volume up+power button combo to simulate a connection. and then it will be flashed. Holy crap. Thank you so much!!.
You are welcome, last three day i also tried flash my up2
Still same problem
..
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
Hi there,
Thanks for the instructions. I have succeeded to install the Oukitel V2.0 ROM on my Ulefone Power 2 and change OEM in Android and fastboot but still no success to flash the final Ulefone Power 2 phone ROM from the Ulefone web site. The flash process starts but after two or three download steps the flash tool (3.1620 in administrator mode) stops still with the STATUS_SEC_IMGHDR_TYPE_MISMATCH error.
I have also tried with another ROM coming from another site, but still same error.
Could perhaps provide me a download link to a ROM that you successfully flashed to the Ulefone Power 2?
Thanks for your help
bletru said:
..
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
Hi there,
Thanks for the instructions. I have succeeded to install the Oukitel V2.0 ROM on my Ulefone Power 2 and change OEM in Android and fastboot but still no success to flash the final Ulefone Power 2 phone ROM from the Ulefone web site. The flash process starts but after two or three download steps the flash tool (3.1620 in administrator mode) stops still with the STATUS_SEC_IMGHDR_TYPE_MISMATCH error.
I have also tried with another ROM coming from another site, but still same error.
Could perhaps provide me a download link to a ROM that you successfully flashed to the Ulefone Power 2?
Thanks for your help
Click to expand...
Click to collapse
Look in your inbox, i wrote you a private message.
bletru said:
..
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
Hi there,
Thanks for the instructions. I have succeeded to install the Oukitel V2.0 ROM on my Ulefone Power 2 and change OEM in Android and fastboot but still no success to flash the final Ulefone Power 2 phone ROM from the Ulefone web site. The flash process starts but after two or three download steps the flash tool (3.1620 in administrator mode) stops still with the STATUS_SEC_IMGHDR_TYPE_MISMATCH error.
I have also tried with another ROM coming from another site, but still same error.
Could perhaps provide me a download link to a ROM that you successfully flashed to the Ulefone Power 2?
Thanks for your help
Click to expand...
Click to collapse
That will help many others like me.please post the ule stock rom you flashed and the flash tool.
SUNRAY888 said:
Hi sm00th4f3
I add some advices to Vivanyok instruction by red letters --->
I have managed to resolve this with a lot of help from Vivanyok on 4pda.
1. Make a backup of your NVRAM and NVDATA, a full ROM backup if you can.
2. Download Oukitel K6000 Plus ROM v2.0. Only this version will work.
3. Flash it. It will actually work just fine, no errors. I've used the latest SPFT.
4. Boot the phone into Android. In Developer Options, enable OEM Unlock.
5. Reboot into fastboot, do fastboot oem unlock.
OR enabled usb debug, accept connection between your PC and Ulephone and send command
fastboot reboot bootloader
after that
fastboot oem unlock
6. After this, you can simply flash any Ulefone ROM for Power 2. Win!
on this step i had a lot issue with insuffitient buffer under SP Flash tool, but yesterday i win too.
be careful :
after oem unlocking you should NOT reboot ulephone to Android,let phone stay connected to PC
try use #SPMultiPortFlashDownloadProject version 3.1620 - only this soft help me,earlier i tried v.3.1636 but always error appear.
and when i started flashing i stayed ulephone connected to usb (i dont disconnect phone after oem unlocking) and i simulated connection by long press volume UP + Power buttons. You can control connection by default PC sound.
due in SPMultiPortFlashDownloadProject other interface i did not change flashing type, it was firware update by default.
After that my ulefone become alive.
7. Restore NVRAM and NVDATA.
good luck, if any questions ask me on 4pda.ru
Click to expand...
Click to collapse
cannot find the up2 rom which can be flashed after flashing Oukitel K6000 Plus ROM. Please help...
Download Links added. There shouldn't be any problems using my method as long as you think as well.
Be aware that you have to use the Flashtool i linked, the exact same Flashtool Version as mentioned. Otherwise go to my german thread outside of xda to get more detailed pics.
solved my problem
this was the solution for me, thanks a lot....
recovered!
Hello guys! Thanks for the instructions, it worked great! Only thing, the fastboot you supplied has an password, so I used another I found online.
I finally got time to take care of my bricked Power 2 phone, and I got it back to life using the Oukitel method.
The phone works great, I only had to input IMEI numbers manualy.
Is there a need to lock back the bootloader, because now my device says "orange state", your device cannot be trusted?
hm hm.... fastboot allows me to lock the bootloader, but then the phone would reset itself to factory state for security reasons, so I will leave my bootloader unlocked, as I don't want to go trough the phone app installation and getting the settings to my taste
i just updated the zip..there shouldn't be a password anymore. ^^
For us, there isn't really a need to lock the bootloader. Since we can simply install every ota update by downloading the new rom from external sites. Just a reminder: don't use the ota update app since it will brick or just not work, since your bootloader is unlocked.
Ulefon power 2
ULEPHON POWER 2
Oukitel k6000 Plus Roma- ok
SPMultiPortFlashDownloadProject verziju 3.1620 FL-OK, DL FAIL ???? HELP HELP
[email protected]
brumen1 said:
ULEPHON POWER 2
Oukitel k6000 Plus Roma- ok
SPMultiPortFlashDownloadProject verziju 3.1620 FL-OK, DL FAIL ???? HELP HELP
[email protected]
Click to expand...
Click to collapse
don't forget to enable oem unlock (bootloader isn't unlocked yet after you do this)
then fast boot the phone with oukitel rom, unlock the bootloader with adb fast boot unlock
don't let go of the vol button while flashing the phone with multiport flash tools
don't use ulepfhone original cable, mine was not working ok although there was no visual damage to the cable. I used another one that fit the usb port on the phone more firmly
bad_ri said:
don't forget to enable oem unlock (bootloader isn't unlocked yet after you do this)
then fast boot the phone with oukitel rom, unlock the bootloader with adb fast boot unlock
don't let go of the vol button while flashing the phone with multiport flash tools
don't use ulepfhone original cable, mine was not working ok although there was no visual damage to the cable. I used another one that fit the usb port on the phone more firmly
Click to expand...
Click to collapse
The Original Cable is fine...the problem might only be with yours.
brumen1 said:
ULEPHON POWER 2
Oukitel k6000 Plus Roma- ok
SPMultiPortFlashDownloadProject verziju 3.1620 FL-OK, DL FAIL ???? HELP HELP
[email protected]
Click to expand...
Click to collapse
Read the thread, it's not that difficult.
sm00th4f3 said:
The Original Cable is fine...the problem might only be with yours.
Click to expand...
Click to collapse
maybe, just told what happened in my case, the original cable was bad from the first day
good luck with the flash
Hi !
I've attempted to deal with the devil by trying to root my Pioneer XDP-300R resulting in a bootloop problem (device is stuck on "Powered by Android" screen).
I attempted to flash a boot.img for a Onkyo DX-P1 (which is the same firmware), and still I haven't progressed.
No firmware, update or imgs are provided on Pioneer's website.
I still have access to fastboot (OEM is LOCKED, so I can't boot TWRP and such) in bootloader mode and adb push (no shell) in recovery mode.
Do you guys have any idea how to sort it out ?
Edit :
I managed to make my device go into Qualcomm's emergency download mode.
Here's how to :
1 - Make sure the device is completely off and unplugged from USB.
2 - Install QPST V2.7.474 (not enough posts to share url, but I can PM it).
3 - Install QDLoader Drivers (same as #2).
4 - Simply press and hold the "Play" button while connecting it to your computer, the device manager should see a "Qualcomm 9008 port" listed in Ports while the player's screen stays black.
5 - Do the Carlton (important step !)
Now, if anyone possessing a FUNCTIONAL AND ROOTED Pioneer XDP-300r is reading this and willing to help, can you get in touch with me ?
Together, we could manage to save all the other devices from soft-bricking.
All I would need from you is some time, hard disk space and patience to sort it out.
Please <insert_your_name_here>, you're my only hope !
Edit #2 :
Thanks to minotauri's great help, we managed to get a FULL rom backup, split the partitions to files and generate all the files needed for QFIL.
ErrOzz has been given access to this, hoping that he'll try it out soon.
If that works, I'll link you the files and write the walkthrough to bring you DAP back to life.
minotauri's contributions are not in rest tho, he managed to also successfuly patch TWRP for the device, so anyone can securely flash things from there now.
For anyone reading this thread : you're not the only one who screwed things up, we did too but we might have the cure. Hang in there !
grogcw said:
Hi !
I've attempted to deal with the devil by trying to root my Pioneer XDP-300R resulting in a bootloop problem (device is stuck on "Powered by Android" screen).
I attempted to flash a boot.img for a Onkyo DX-P1 (which is the same firmware), and still I haven't progressed.
No firmware, update or imgs are provided on Pioneer's website.
I still have access to fastboot (OEM is LOCKED, so I can't boot TWRP and such) in bootloader mode and adb push (no shell) in recovery mode.
Do you guys have any idea how to sort it out ?
Edit :
I managed to make my device go into Qualcomm's emergency download mode.
Here's how to :
1 - Make sure the device is completely off and unplugged from USB.
2 - Install QPST V2.7.474 (not enough posts to share url, but I can PM it).
3 - Install QDLoader Drivers (same as #2).
4 - Simply press and hold the "Play" button while connecting it to your computer, the device manager should see a "Qualcomm 9008 port" listed in Ports while the player's screen stays black.
5 - Do the Carlton (important step !)
Now, if anyone possessing a FUNCTIONAL AND ROOTED Pioneer XDP-300r is reading this and willing to help, can you get in touch with me ?
Together, we could manage to save all the other devices from soft-bricking.
All I would need from you is some time, hard disk space and patience to sort it out.
Please <insert_your_name_here>, you're my only hope !
Click to expand...
Click to collapse
Hi - I saw your post on Head-Fi (antdroid over there). Let me look into this!
Here is a bunch of system dump images and qcn files: https://drive.google.com/drive/folders/1diqQ8LE-yG4b-WZFB_OPcQp2rDUp9BbV?usp=drive_open
Hello.
How can I write boot from qdload 9008 state?
Hi !
From the edl / qdload 9008 state, you can't afaik.
Here's how I think you can :
1 - Unplug your device from USB and power it off from whatever state it is.
2 - Power it on pressing Power + Previous button (keep holding, you should be "stuck" on the penguin logo).
3 - Connect your USB.
4 - Check that you have a Android ADB Device in your device manager (install drivers manually if you have an Unknown device).
5 - Grab any fastboot from the internet if you don't already have it (I'll PM you my gdrive, it's there for exemple).
6 - From CMD, go to fastboot directory. (cd <my_folder_with_fastboot>).
7 - Type in : fastboot devices
If fastboot sees your device, you're on the good path, else, check your driver / connection / reboot to fastboot "penguin" state.
8 - Type in : fastboot oem device-info
If it replies
(bootloader) Device unlocked: true
among others, you're in a good, good way, else, you're screwed by now, but we are working on it.
9 - If all the precedent are fulfilled type :
fastboot flash boot <my_boot_image.img>
10 - Mandatory Carlton.
I hope you'll be in the right path all the way, if you're stuck somewhere or if your bootloader is locked, please let me know.
Cheers !
ErrOzz said:
Hello.
How can I write boot from qdload 9008 state?
Click to expand...
Click to collapse
I was successful in creating a recovery (twrp) for this device.
https://www.antdroid.net/2019/02/pioneer-xdp-300r-root-twrp-recovery.html?m=1
also created a XDA thread here: https://forum.xda-developers.com/android/development/pioneer-xdp-300r-digital-audio-player-t3902949
Feel free to PM me if you have questions or we can work it through here
Hi,
I have the same problem. I am able to get qdload 9008 state from here now. However, after unplug and followed grogcw's hints, the device is not recognized again. Also, the device hasn't ennobled debug mode before too. All the adb and fastboot commands return no device.
Hopefully can get more help here.
---------- Post added 28th February 2019 at 12:16 AM ---------- Previous post was 27th February 2019 at 11:58 PM ----------
minotauri said:
I was successful in creating a recovery (twrp) for this device.
https://www.antdroid.net/2019/02/pioneer-xdp-300r-root-twrp-recovery.html?m=1
also created a XDA thread here: https://forum.xda-developers.com/android/development/pioneer-xdp-300r-digital-audio-player-t3902949
Feel free to PM me if you have questions or we can work it through here
Click to expand...
Click to collapse
Is there anyway to flash TWRP and so with QDLoader?
I believe he is on vacation for another week and half. If you haven't enabled the bootloader unlock option within Android, then my recovery method may not work since it may not let you flash the recovery.
You can try to fastboot boot recovery.img though
Hi ! I'm back from vacation, but I still haven't my device around.
Any user willing to test are welcome to reply or PM me !
Let's have all the bricked units working, shall we
grogcw said:
Hi ! I'm back from vacation, but I still haven't my device around.
Any user willing to test are welcome to reply or PM me !
Let's have all the bricked units working, shall we
Click to expand...
Click to collapse
How can we get started?
We actually did start probing stuff around, and we are missing something in the "full restoration process", so we're stuck for now.
Sahara protocol still is a mystery for us, and we can't get pass an error.
I think we don't actually have the right programmer_firehose.mbn for our device, but if it's not this, I'm basically out of ideas. (we might need an "QFIL expert" on this)
I still don't have my device around and feeling dumb about this.
Anyway, all the files and tools required to try probing around are in my gdrive and I can PM the link (as I still can't post it right away) if anyone is interested.
Thanks for trying to help or actually help everyone !
Cheers !
Hello,
I try to root my xdp-300r,after reboot have bootloop result.
I don't know how to reflash systme.img.
can suggest any repair plan,thank you~
Was able to unbrick device. Here are the steps TO DO IT
grogcw said:
hi !
I've attempted to deal with the devil by trying to root my pioneer xdp-300r resulting in a bootloop problem (device is stuck on "powered by android" screen).
I attempted to flash a boot.img for a onkyo dx-p1 (which is the same firmware), and still i haven't progressed.
No firmware, update or imgs are provided on pioneer's website.
I still have access to fastboot (oem is locked, so i can't boot twrp and such) in bootloader mode and adb push (no shell) in recovery mode.
Do you guys have any idea how to sort it out ?
edit :
i managed to make my device go into qualcomm's emergency download mode.
Here's how to :
1 - make sure the device is completely off and unplugged from usb.
2 - install qpst v2.7.474 (not enough posts to share url, but i can pm it).
3 - install qdloader drivers (same as #2).
4 - simply press and hold the "play" button while connecting it to your computer, the device manager should see a "qualcomm 9008 port" listed in ports while the player's screen stays black.
5 - do the carlton (important step !)
now, if anyone possessing a functional and rooted pioneer xdp-300r is reading this and willing to help, can you get in touch with me ?
Together, we could manage to save all the other devices from soft-bricking.
All i would need from you is some time, hard disk space and patience to sort it out.
please <insert_your_name_here>, you're my only hope !
edit #2 :
thanks to minotauri's great help, we managed to get a full rom backup, split the partitions to files and generate all the files needed for qfil.
Errozz has been given access to this, hoping that he'll try it out soon.
If that works, i'll link you the files and write the walkthrough to bring you dap back to life.
Minotauri's contributions are not in rest tho, he managed to also successfuly patch twrp for the device, so anyone can securely flash things from there now.
For anyone reading this thread : You're not the only one who screwed things up, we did too but we might have the cure. Hang in there !
Click to expand...
Click to collapse
i was able to unbrick my device
dantuko said:
all credits go to anthony nguyen aka minotauri. Thank you!
requirements:
samsung drivers installed
windows 10 (i have the windows 10 pro installed)
oem unlock
usb debbuging selected prior to brick
install the latest samsung drivers
install fastboot/adb drivers
stock-boot.img provided by minotauri
the steps are as follows:
the device must be in recovery mode an plugged to the computer. I was on stock recovery
open device manager in windows, look for anything android and delete it and choose to delete the drivers
refresh device manager for new devices (keep only the xdp-300 android connected)
right click on the android device and click on update drivers
select browse my computer for driver software
click on let me pick from a list of available drivers
unselect show compatible drivers (if you see a samsumg driver here, select it. If not try generic windows adb drivers)
seletct google adb drivers (this is the one that worked and it's under samsung drivers)
i performed the steps 1 through 8 a few times until the computer categorized the device as adb
open a command prompt, navigate to the directory where fastboot is installed and type: Fastboot devices (you should have a device listed here)
type: Fastboot oem unlock (this unlocks the bootloader)
after copying stock-boot.img to the root of the your fastboot directory, type: Fastboot flash boot stock-boot.img (reboot)
after the reboot you should see normal boot
if you want twrp and root follow the instructions here: https://forum.xda-developers.com/android/development/pioneer-xdp-300r-digital-audio-player-t3902949 all credits go to anthony nguyen.
i installed twrp the latest supersu pro, viper4android, root browser, busy box pro and everything works perfectly.
:fingers-crossed::fingers-crossed::fingers-crossed:good luck to you e n j o y ! ! !:fingers-crossed::fingers-crossed::fingers-crossed:
i am not an android programmer so i won't be able to help you from that perspective, but i a software engineer so i maybe able to answer some questions.
There is no guarantee this method will work for you but it did work for me
I can provide a TWRP backup file for you to restore your device
Click to expand...
Click to collapse
I have a rooted xdp300r rooted
ralf05 said:
Hello,
I try to root my xdp-300r,after reboot have bootloop result.
I don't know how to reflash systme.img.
can suggest any repair plan,thank you~
Click to expand...
Click to collapse
It was bricked and I was able to fix it and root it
Help !!!
Hello
Gentlemen, help me! I've broken my device
I hit the whole system on my xdp300r. What can I do in this case ??? Only I can turn on TWRP and nothing more.
[email protected]
---------- Post added at 05:55 PM ---------- Previous post was at 05:51 PM ----------
dantuko said:
i was able to unbrick my device
Click to expand...
Click to collapse
Help !!!
dantuko said:
i was able to unbrick my device
Click to expand...
Click to collapse
Hello
Could I ask you for a backup file? Unfortunately, I lost the systemThank you very much.
Greetings.
[email protected]
stefan999 said:
Hello
Could I ask you for a backup file? Unfortunately, I lost the systemThank you very much.
Greetings.
[email protected]
Click to expand...
Click to collapse
I UPLOADED THE BACKUP FILE TO MY GOOGLE DRIVE
https://drive.google.com/drive/folders/1vM7Z12w3CsbutSr54lY4tTdzyN1jurpp?usp=sharing
dantuko said:
I UPLOADED THE BACKUP FILE TO MY GOOGLE DRIVE
https://drive.google.com/drive/folders/1vM7Z12w3CsbutSr54lY4tTdzyN1jurpp?usp=sharing
Click to expand...
Click to collapse
Here is a few items to note about the image:
You must have twrp installed and accessible in order to restore this image.
First time booting after the restore will take a long time, so have a cup of coffee and let it do it's thing.
Every time you boot the OS will perform application optimization, it doesn't bother me so I have not even looked into it.
After you boot connect to your WIFI and open Google Play to set up your account
If you want to use Viper4Android, download and install busybox, then open settings, go to apps and disable Musicfx, then reboot and turn Viper4Android on.
Good luck
dantuko said:
Here is a few items to note about the image:
You must have twrp installed and accessible in order to restore this image.
First time booting after the restore will take a long time, so have a cup of coffee and let it do it's thing.
Every time you boot the OS will perform application optimization, it doesn't bother me so I have not even looked into it.
After you boot connect to your WIFI and open Google Play to set up your account
If you want to use Viper4Android, download and install busybox, then open settings, go to apps and disable Musicfx, then reboot and turn Viper4Android on.
Good luck
Click to expand...
Click to collapse
Thanks for answer and sharing your files. Unfortunately, there is some error when trying to restore in TWRP.
I packed all the items from your disk in ZIP and downloaded to the SD card .
I'm getting an error about the content: no MD5 file found Failed to map file'/external_sdxxxxxx-Full BACKUP.zip'
Error instaling zip file
. Do you have an idea why this is happening?
twrp settings
stefan999 said:
Thanks for answer and sharing your files. Unfortunately, there is some error when trying to restore in TWRP.
I packed all the items from your disk in ZIP and downloaded to the SD card .
I'm getting an error about the content: no MD5 file found Failed to map file'/external_sdxxxxxx-Full BACKUP.zip'
Error instaling zip file
. Do you have an idea why this is happening?
Click to expand...
Click to collapse
You need to change settings in twrp not to check md5 checksum, if it doesn't work then i'll create one with checksum.