Related
While flashing a rom, sometimes we get a "status 7 error". This Guide helps you to get out from it, and flash your favourite rom. Let's get started.
Move to META_INF > COM > GOOGLE > ANDROID by extracting the rom.
Here you will find a file "updater-script". Rename this file as updater-script.doc (microsoft word format) or use notepad++ (preferably)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.
Double click to open it( microsoft word preferred)
delete text, starting from "assert ....... till the semicolon ( of the last getprop command).
(See the image in the attached file for carefully deleting the lines. Click this link.)
Save the file now.
Again rename the file, and delete the .doc extention
Now go back and zip these files again. and you will get a zipped rom.
And the status 7 error has now been removed!
---
Siddharth121 said:
hey!
while flashing roms, many times we get a "status 7 error". while searching in many threads, we do not get how to resolve it. i will tell you each and every thing step by step
so i made a NOOB FRIENDLY WAY TO RESOLVE STATUS 7 ERROR
make sure that the rom you have downloaded matches your phone model, if you flashed some other rom, you may hard brick your device.
1. First extract your rom (for example using 7-zip)
2. Go to the folder META_INF > COM > GOOGLE > ANDROID
3. Here you will find a file "updater-script"
4. Rename this file as updater-script.doc (microsoft word format)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.
5. Double click to open it( microsoft word preferred)
6. delete text, starting from "assert ....... till the semicolon( of the last getprop command. (see image in attached file-lines to delete)
7. Now save the file
8. Again rename the file, and delete the .doc extention
9. now go back to the main rom folder where you extracted the 3 files. zip these files again. and you will get a zipped rom.
and the status 7 error has now been removed!:good:
happy flashing :victory::victory:
at last, as you read in every post, i am not responsible for any bricked device.
Click to expand...
Click to collapse
have you already try to cook rom using android kitchen?
I saw android kitchen. But it didn't supported my p3100. Ive rooted my htc day before yesterday. I'll try that surely :thumbup:
But why?..
Sent from my HTC One X+ using xda premium
Siddharth121 said:
I saw android kitchen. But it didn't supported my p3100. Ive rooted my htc day before yesterday. I'll try that surely :thumbup:
But why?..
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
because every time i use that to cook rom for my samsung galaxy gio the installation is aborted and error status 7 when i am flashing it
Do the above mentioned, actually the recovery checjs for the device version and all before flashing.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Do the above mentioned, actually the recovery checjs for the device version and all before flashing.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
yeah maybe that is the main problem dude it is really hard to work with kitchen
Yepp. It is, but it reduces your harwork.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
Yepp. It is, but it reduces your harwork.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
maybe in deodexing a stock rom should the first one that really helps
flash the zip ,go to advanced option "show logs"
delete the lines which shows error like no file or directory in updater script
simple way
percy_g2 said:
flash the zip ,go to advanced option "show logs"
delete the lines which shows error like no file or directory in updater script
simple way
Click to expand...
Click to collapse
is that method is tested and proven?
badagila said:
is that method is tested and proven?
Click to expand...
Click to collapse
Yeah
Sent from my LT22i using Tapatalk 2
percy_g2 said:
Yeah
Sent from my LT22i using Tapatalk 2
Click to expand...
Click to collapse
have you try to cook rom using dsixda kitchen?
so the advice is to remove the device check?
How about a tip on how to use the proper device id or name?
So where do I look in the device to use the name that works?
That would be better imho.
I did try to use the values in the build.prop file from the running device, but that did not work eiter.
Now i'm getting status 4 error
i was getting status 7 error. Searched the forum and found this thread. I followed the directions to take off the lines from updated script files, but now i'm getting status 4 update. Can anyone recommend me how i can take care of status 4 error?
I can't flash any custom rom from recovery. Please help.
nulfinis said:
Hi,
I still get status 7 after using this guide.
any advice?
Click to expand...
Click to collapse
My Android Solutions
[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
Error 7
xsenman said:
My Android Solutions
[27] Problem:- ClockworkMod Recovery giving Status 7 error "Installation aborted".
Solution:- One or some of the prerequisite requirement for the needed upgrade is missing or corrupted . So you may need to identify and replace that requirement for the installation to continue. Most likely could be due to wrong bootloader, wrong CWM, Wrong IMEI, Wrong Radio etc
I have had Error 7 due to delete many apps and unnecessary files in the rom. I resolved my problem flashing again the rom (previous rom) that I was removing apps and files. Then, I flash the new rom and problem resolved. Regards.
P.D. I have FXP238 CM10 installed and running ok.
Click to expand...
Click to collapse
Siddharth121 said:
1. First extract your rom (for example using 7-zip)
2. Go to the folder META_INF > COM > GOOGLE > ANDROID
3. Here you will find a file "updater-script"
4. Rename this file as updater-script.doc (microsoft word format)
(in some pc, extensions are nor visible. to make them visible, follow these steps)
Open Folder Options by clicking the Start button , clicking Control Panel, clicking Appearance and Personalization, and then clicking
Folder Options.
Click the View tab, and then, under Advanced settings, do one of the following:
To display file extensions, clear the Hide extensions for known file types check box, and then click OK.
5. Double click to open it( microsoft word preferred)
6. delete text, starting from "assert ....... till the semicolon( of the last getprop command. (see image in attached file-lines to delete)
7. Now save the file
8. Again rename the file, and delete the .doc extention
9. now go back to the main rom folder where you extracted the 3 files. zip these files again. and you will get a zipped rom.
Click to expand...
Click to collapse
hi, i follow all the instruction, but im still getting error, this time its "status 6"
wrong thread lol
thx for good work
Here's a guide on how to :
1| Root your Xperia U
2| How to unlock the bootloader
3| CWM Installation
4| Flash of a custom ROM
Here's the guide to obtain root acces on firmware .54 [LOCKED BOOTLOADERS !]
Requires :
1| PC running windows vista or abova
2| USB Cable
3| XU
Let's get rooting !
1| Download kernel C.10 : DOWNLOAD and extract kernel in a folder of your desktop {ES : kernel}
2| Download bin4ry's script : DOWNLOAD
3| Download Flashtool : WEBSITE
4| Open and install Flashtool
5| Connect your Xperia U with USB cable and enable "usb debug" {settings > developer options > tick "usb debugging"}
5A| Go to C: > Flashtool > drivers > Flashtool drivers.exe > open and search for "Xperia U,P,Sola and Go Drivers" , "Flashmode" and "Fastboot" drivers
6| MAKE SURE THAT YOU HAVE ENABLED USB DEBUGGING AND UNKNOW SOURCES ! MOST IMPORTANT : Unable the PIN code !!!!
For usb debug : settings > developer options > usb debug
For unknow sources : settings > security > unknown sources
7| Power off Xperia U. Press volume down button while connecting usb cable and you should see a blue LED on your Xperia U. Flashtool should show you this : "Device connected in fastboot mode"
8| Now on PC press the "Flash" button and select "Fastboot mode" > "select kernel to flash" > search in which directory you put kernel {es. desktop}. Once select kernel select "Open"
9| Wait a while
10| Once flashed kernel,reboot your phone
11| Now your phone should be dark and really laggy,but keep calm
12| Connect XU to PC with usb cable
13| Open "Root_with_Restore_by_Bin4ry_v13" and open the "runme.bat file"
14| Select "normal mode" press 1 on your PC
15| This is what you should see :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
16| Now press enter and wait....
17| On your XU you should see the app "Backup and Restore" asking for a restore of a backup called "ROOTME.TAR". Select yes,restore backup
18| Now the phone should automatically reboot
19| You have root acces on firmware .54 !
gangsterjoop said:
Thread can stay in development, but no need for reserving posts. If you would need an extra post the mods can insert one.
Click to expand...
Click to collapse
Yes,i need of three / four extra posts
-----------------------------------------------------------------------------------
Here's the guide on how to unlock the bootloader !
This passage will void your warranty so do this only if you know what are you doing. By unlocking bootloader you can flash more custom ROMS then on unlock bootloaders and you can also flash custom kernels !
You will also lose your apps !
Start !
1| On your XU go to dialer and write
Code:
*#06#
and copy your IMEI on a sheet
2| DOWNLOAD this file. Inside there are fastboot and drivers.
3| Extract "fastboot" folder in a directory {es : desktop}
4| Extract "drivers" folder and install drivers. WARNING : If you have installed drivers before,do not install them again
5| Go to http://unlockbootloader.sonymobile.com/instructions and click "Continue"
6| Now select "Yes,I'm sure" and "I accept"
7| Now insert name,email and IMEI without the last number
8| Now check your e-mail box, you should find an email from sony .You will receive an unlock code that you will copy on a sheet
9| Connect XU in fastboot mode {volume down and usb cable}
10| Open "fastboot" folder and press "S-H-I-F-T" + right click > select "Open Command Prompt here"
11| Type this :
Code:
fastboot.exe -i 0x0fce getvar version
12| If drivers are succesfully installed,you should get this answer :
Code:
05
13| Ok,now type this :
Code:
fastboot.exe -i 0x0fce oem unlock 0xKEY
IMPORTANT : REPLACE "KEY" WITH THE UNLOCK CODE THAT YOU RECEIVED VIA E-MAIL !
14| When finished,device should automatically reboot
15| You have unlock bootloader ....Haters gonn HATE:laugh:
Here's the guide on how to install CWM !
Unlock bootloaders :
Flash a kernel which has CWM [es. Transcendence etc.]
Locked bootloaders :
1| DOWNLOAD Atis' CWM
2| Connect your XU with usb debug enabled
3| Open "install.bat" and follow the instructions
This is a great guide to noobs! Cool and awesome and very simple to follow through! Thanks mate!
Tapatalk sig: I believe in god but I also believe in Metal. Does that makes sense? I hope so.
---------- Post added at 07:21 PM ---------- Previous post was at 07:20 PM ----------
We should request to pin this post at top so noobs will see it!
Tapatalk sig: I believe in god but I also believe in Metal. Does that makes sense? I hope so.
PM moderators and make this as stickies for easy access
Sent from my Xperia U using Tapatalk 4
Elwino2.3 said:
PM moderators and make this as stickies for easy access
Sent from my Xperia U using Tapatalk 4
Click to expand...
Click to collapse
Thanks buddies
Isn't Volume Down + USB = flash mode and Volume Up + USB = fastboot? Or it depends on XU version (2011/2013)?
Nice tutorial BTW
Sent from my ST25i using xda premium
This guide for unlock bl Is for "unlock allowed : no" device ?
the Fastboot d/l link at unlockin bloader section doesnt work... please @DroidModderXtreme upload another...
sorry for this sony noobish cuz i always sammy b4 : How to enter CWM recovery mode??? please n sorry..
Does rooting void my warranty?
9| Connect XU in fastboot mode {volume down and usb cable}
Volume down and usb cable?
I think it's volume UP and usb cable...forgive me if i am wrong
kwstas 13 said:
9| Connect XU in fastboot mode {volume down and usb cable}
Volume down and usb cable?
I think it's volume UP and usb cable...forgive me if i am wrong
Click to expand...
Click to collapse
You right bro it volume up
________________________________
Phone : Xperia U
Rom : Stock ICS modded
Kernel : stock
Bootloader : Unlocked ( thank god)
VocaloidBoy said:
You right bro it volume up
________________________________
Phone : Xperia U
Rom : Stock ICS modded
Kernel : stock
Bootloader : Unlocked ( thank god)
Click to expand...
Click to collapse
please confirm for me as noobish sony user :
vol up + usb = fastboot ???
vol down + usb = flashtool ???
Adam Hui said:
please confirm for me as noobish sony user :
vol up + usb = fastboot ???
vol down + usb = flashtool ???
Click to expand...
Click to collapse
Yes B that right
vol up + usb = fastboot
vol down + usb = flashmod
Error with flashing Kernel.sin
Code:
11/001/2013 20:01:12 - INFO - <- This level is successfully initialized
11/001/2013 20:01:12 - INFO - Flashtool Version 0.9.12.1 built on 2013-06-04 22:50:00
11/001/2013 20:01:13 - INFO - Device connected with USB debugging on
11/001/2013 20:01:14 - INFO - Connected device : Sony Xperia U
11/001/2013 20:01:14 - INFO - Installed version of busybox : N/A
11/001/2013 20:01:14 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
11/002/2013 20:02:41 - INFO - Please wait device is rebooting into fastboot mode (via ADB)
11/002/2013 20:02:47 - INFO - Device will soon enter fastboot mode
11/002/2013 20:02:47 - INFO - Device disconnected
11/002/2013 20:02:48 - INFO - Device connected in fastboot mode
11/003/2013 20:03:06 - INFO - Selected kernel (boot.img or kernel.sin): C:\kernel.sin
11/003/2013 20:03:06 - INFO - Flashing selected kernel
11/003/2013 20:03:06 - INFO - sending 'boot' (5293 KB)...
11/003/2013 20:03:06 - INFO - FAILED (remote: The Device must be rooted first)
11/003/2013 20:03:06 - INFO - finished. total time: 0.002s
11/003/2013 20:03:06 - INFO - FASTBOOT Output:
sending 'boot' (5293 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.002s
11/003/2013 20:03:06 - INFO - Please check the log before rebooting into system
Any tips? Version : 6.1.1.B.1.54
I don't respond for What-So-Ever done any damage to your Phone, You must accept this risk with yourself.
Hi all,
I'm proud to present my useful tools. SRK Tool ,it's a tools for noob and advance user.This tool is connecting between LG G3 and computer that is a reason you must Enable USB Debugging mode befor use SRKTool
Download link SRKtool_1.0.5_droidth.zip:
SRKtool_1.0.5_droidth.zip
Download link SRKtool_1.0.4_droidth.zip:
SRKtool_1.0.4_droidth.zip
Download link SRKtool_1.0.3_droidth.zip:
SRKtool_1.0.3_droidth.zip
Download link SRKtool_1.0.2_droidth.zip:
SRKtool_1.0.2_droidth.zip
Change logs:
1.0.5
ROOT
- ROOT+TWRP For F320S/L/K
BACKUP
- Backup Sensor
- Backup Cust
- Backup All importance partition
Utility
- Nuke Download Mode - (When No Recovery,Can't Boot)
- Fix Recovery Mode - via fastboot mode (When No Recovery,Can't Boot) (ALL Variant)
Other
- Change 7z to 7-Zip Extra (Highest compression ratio/Fast compression) Support 32bit/64bit Windows
1.0.4
- Send Command (Spacial Mode for fix device)- NEED DOWNLOAD MODE.
- New Bump Kernel (30e) for D802
- Fix bug and improving program Make it's stable
- Redegin UI Program
1.0.3
- Adding Fix fastboot mode started
- How to Flash KDZ/TOT/Extract KDZ
- Check current firmware
- Link to firmware KDZ warehouse
1.0.2
- Adding feature ROOT+TWRP for LGG3 F400S
- Adding ADB Sideload for install ROM
- VDO Recording screen
- Screen Capture
- Reboot Device
- Update adb to the newest version
1.0.1
- Adding feature ROOT+TWRP for LGG3 D855
1.0
- initial version
Click to expand...
Click to collapse
How to use
1. Download the Unzip
SRKtool_1.0_droidth
2. Enable Debugging mode
3. Plug g3 into Computer
4. Run srktool.exe
5. Enjoy
If you got "MSVCR100.dll is missing" error, install Visual C++ Redistributable.
Download: 32 bit / 64 bit.
64 bit users, install both 32 and 64.
What is SRKTool can do ?
1. In picture as below it's a basic function that you can use very easy. All function I have tested .It is work very well.
- ROOT KitKat/Lollipop Stock Firmware.
- ROOT AND TWRP Lollipop Stock Firmware (LGG2-D802/801,LGG3-D855).
- Enter to Download Mode.
- Leave Downloadmode.
- Enter to Recovery Mode.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. For Advance User [Not For NOOB]
- Nuke Download Mode (Advance User REQUIRE)
- Fix Download Mode - From Nuke Download Mode (Advance User REQUIRE)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Nuke Download Mode make your g3 can't enter to Download Mode But you can enter fastboot mode instead. In fastboot Mode you can fix or use fastboot command to flash all partition of LG g3 Maybe you have to you in spacial.
Before a program nuke Download Mode it will be backup your Download Mode in file backup-laf\backup_droidth-laf.img.You can fix Download Mode from menu Fix Download Mode - From Nuke Download Mode (Advance User REQUIRE)
3. You can make BUMP Kernel for developer
- Make BUMP Kernel (ROOT REQUIRE)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
After unzip SRKtool_1.0.1_droidth find folder
droidth_bump\bump\boot_original
Click to expand...
Click to collapse
Put boot.bin (stock kernel) in that folder then run program after program process complete bump kernel will be stay at
droidth_bump\bump\boot_original\boot_bump
Click to expand...
Click to collapse
4. For Backup and Create your flash-able zip from your current ROM
Backup Fota Partition (ROOT REQUIRE)
Backup BaseBand (ROOT REQUIRE)
Backup EFS Partition (IMEI) (ROOT REQUIRE)
Backup BOOTLOADER (ROOT REQUIRE)
Create your flash-able zip from your current ROM (ROOT REQUIRE)
Click to expand...
Click to collapse
After run program .img file that is a output from other process will be stay at
droidth_input\baseband
droidth_input\bootloader
droidth_input\efs
droidth_input\rom
droidth_input\fota
Click to expand...
Click to collapse
and flashable file which you can get it to flash via Custom Recovery it will be stay at
droidth_output
Click to expand...
Click to collapse
5. Another folder DO NOT TOUCH IT
Thank you,
ขอบคุณครับ (In Thai language)
Credit:
1. @Unjustified Dev for send_command
2. @avicohh One Root Script
3. @Skin1980on line bump
4. @jac10000 partition name LG G3
For. any question that want to ask me in private Please Leave a question in facebook group
https://www.facebook.com/groups/1420724551528661/
......... DON'T INBOX TO ME .........
@somboons your tool is awesome ! Very good work, very useful.
Thank you
@somboons: Please change extention of srktool101 to *.bat to modified for F400 variants? Thank anyway!
looks very usefull and great to have
thx alot
Reserved
Στάλθηκε από το MI 2S μου χρησιμοποιώντας Tapatalk
Any chance of getting support for the f460 (G3 Cat6) series? What files would you need (or that i could swap out) to make it happen?
@somboons : you're tool seems to be awesome, but I got one issue; it doesn't detect my phone; it stays on "waiting for device". But when I launch for example "adb devices" in a command prompt, it detects my phone. I got all drivers installed, adb, my phone is rooted, has usb debugging enable. Do you know issue's source?
somboons said:
I don't respond for What-So-Ever done any damage to your Phone, You Accept this risk.
Hi all,
I'm proud to present my useful tools. SRK Tool ,it's a tools for noob and advance user.This tool is connecting between LG G3 and computer that is a reason you must Enable USB Debugging mode befor use SRKTool
Download link SRKtool_1.0.1_droidth.zip:
http://bit.ly/1D8EBI0
How to use
1. Download the Unzip
SRKtool_1.0_droidth
2. Enable Debugging mode
3. Plug g3 into Computer
4. Run srktool.exe
5. Enjoy
What is SRKTool can do ?
1. In picture as below it's a basic function that you can use very easy. All function I have tested .It is work very well.
2. For Advance User [Not For NOOB]
Nuke Download Mode make your g3 can't enter to Download Mode But you can enter fastboot mode instead. In fastboot Mode you can fix or use fastboot command to flash all partition of LG g3 Maybe you have to you in spacial.
Before a program nuke Download Mode it will be backup your Download Mode in file backup-laf\backup_droidth-laf.img.You can fix Download Mode from menu Fix Download Mode - From Nuke Download Mode (Advance User REQUIRE)
3. You can make BUMP Kernel for developer
After unzip SRKtool_1.0.1_droidth find folder
Put boot.bin (stock kernel) in that folder then run program after program process complete bump kernel will be stay at
4. For Backup and Create your flash-able zip from your current ROM
After run program .img file that is a output from other process will be stay at
and flashable file which you can get it to flash via Custom Recovery it will be stay at
5. Another folder DO NOT TOUCH IT
Thank you,
ขอบคุณครับ (In Thai language)
Credit:
1. @Unjustified Dev for send_command
2. @avicohh One Root Script
3. @Skin1980on line bump
4. @jac10000 partition name LG G3
For. any question that want to ask me in private Please Leave a question in facebook group
https://www.facebook.com/groups/1420724551528661/
......... DON'T INBOX TO ME .........
Click to expand...
Click to collapse
Post^^
Thank you. This worked on my LG G3 D855 running Lollipop 5.0
casual_kikoo said:
@somboons : you're tool seems to be awesome, but I got one issue; it doesn't detect my phone; it stays on "waiting for device". But when I launch for example "adb devices" in a command prompt, it detects my phone. I got all drivers installed, adb, my phone is rooted, has usb debugging enable. Do you know issue's source?
Click to expand...
Click to collapse
Try to manual enter to download mode. then capture screen of device manager to me just like this
somboons said:
Try to manual enter to download mode. then capture screen of device manager to me just like this
Click to expand...
Click to collapse
Here the capture screen:
Edit: When I manually enter in Download Mode, your app detects my phone, but when I ask to your app to enter my phone in Download Mode, same issue: not detected
casual_kikoo said:
Here the capture screen:
Edit: When I manually enter in Download Mode, your app detects my phone, but when I ask to your app to enter my phone in Download Mode, same issue: not detected
Click to expand...
Click to collapse
Make sure u plug phone only in usb port. Remove all device that plug in usb port. Can you show Ports in device manager ?
somboons said:
Make sure u plug phone only in usb port. Remove all device that plug in usb port. Can you show Ports in device manager ?
Click to expand...
Click to collapse
My device manager, sorry I upload wrong picture...
casual_kikoo said:
My device manager, sorry I upload wrong picture...
Click to expand...
Click to collapse
it doesn't detect your phone,re-install driver again.
Revert backup to 1.0.1 it can't ROOT+TWRP on F400L/K.
This tool is working for F400S on Lollipop rom.
Works perfect with D855 16GB T-Mobile Germany...
Rooted + TWRP on V20H...i can´t believe it :laugh::laugh::laugh:
Thank you for this great Toolkit :good::good::good:
thanks sooooooo much for Easy method @somboons
Thank you
TWRP, installed on D855 stock lollipop.
casual_kikoo said:
Here the capture screen:
Edit: When I manually enter in Download Mode, your app detects my phone, but when I ask to your app to enter my phone in Download Mode, same issue: not detected
Click to expand...
Click to collapse
In my case , my computer don't have msvcr100.dll , after install it , everything working.
good work!!
For a week now,i have been trying to troubleshoot these issues and they ended up in vain.
The problem occurred,when i first tried to flash CM recovery ,i Typed in "FASTBOOT oem unclock",then everything went into this havoc.
The the phone ,boots into Fastboot mode Only when i press the (Vol Urip+power).
No recovery is Present ,when i try the (Vol Down + Pwer) I get the One plus symbol ,nothing else.
No Rom is present ,so i cant just load into a Rom ,to try something via that way
The images show a few ways that i have tried to solve this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since i am NOT able to go into recovery ,i am stuck.
Please try helping me solve this ,Thanks !
[The methods that i have previously tried before asking this is ,
Tried to use the WinDroid Toolkit ,almost a couple other threads regarding bootloop(since i am unable to get the Recovery screen itself) all that didn't help]
Edit: If above links of image don't load
http://postimg.org/image/awmyeceiz/
http://postimg.org/image/iulytqh6z/
arundp95 said:
For a week now,i have been trying to troubleshoot these issues and they ended up in vain.
The problem occurred,when i first tried to flash CM recovery ,i Typed in "FASTBOOT oem unclock",then everything went into this havoc.
Click to expand...
Click to collapse
Ok, try this
still stuck.
Thanks for the tip.
I tried that method and this is wher i am stuck at.
When i connect the phone instead of getting Qualcomxxxxx i get RELINK HS-USB QDLOADER 9008(com3)
and because of this the msm downloader,doesnt detect the phone and its stuck there.
Please help.
Thank You
arun
[Solved]
It finally got detected then stated up .
[if anyone gets stuck with this problem,i am more than willing to help you solve it .Ping me ]
Thank you
arun
arundp95 said:
It finally got detected then stated up .
[if anyone gets stuck with this problem,i am more than willing to help you solve it .Ping me ]
Thank you
arun
Click to expand...
Click to collapse
Do mention here. It will be helpful for everyone.
[Solved] OnePlus X Brick
saurabh40629 said:
Do mention here. It will be helpful for everyone.
Click to expand...
Click to collapse
Sure.
As the Post above mentioned (in the first comment) ,thats the way to go to fix a Hard bricked / bootloop stuck / no Display.
But if you encounter any problems or issues like i did (the QualCom 9008 ...).I did these
Note : all downloads for this adventure are already present in that guide ,Give it a thumbs up after you fix it as it just recovered a potato , link
HTML:
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Step 1: Requirements
Download the qualcom drivers,fastboot-adb all of that,even though i had them installed,i did a clean installation.
Download the Huge 800MB file (the Recovery tool).
Unzip them to the Desktop, 2 folders (1 for the Qualcomm driver,another for the msm).
Step 2: Set-up
Follow the turning off drive signature process from the post above ,Its fairly simple(press shift restart,advanced,f7 restart).
Install adb-drivers.
Switch off phone (press Power Button for 12 sec or so )till it vibrates and display is blank.
Press the Power Up button and plug in the Phone to your comp
If your Internet connection is turned on,mostly windows will itself download and install the driver(qualcom-xxx) for this device.
Step 3:
Now Unplug the phone.Switch it off(your display will be blank ,to begin with but remove phone press power button 12 sec (wait for vibrate )
Press power button up and plug it back in the comp.When you do this navigate to the Device manager tab ,A new entry in that table will be present Ports & Coms or so. If you dont have this ,no worries (go back to the First step and try to get your drivers re-Installed) .
Now that you have located your com port, RELINK HS-USB QDLOADER 9008(com3) in my case( you might have anything else ,but getting this is crucial).
On that Entry right click and go to Properties.In properties > Driver Tab > Update Driver
Once you click Update, Click on Browse my comp for driver
Then Click on LET ME PICK FROM A LIST
UNCHECK the SHOW COMPATIBLE HARDWARE // Have to do this !
Under Manufacturer,FIND Qualcomm Incorporated
Under MODEL,Select QUALCOMM HS- USB MSM DIAGNOSTICS xxxx (i chose the first entry,BUT MSM is integral).
Install that .RESTART COMP,IT'll PROMPT.
UNPLUG PHONE ,SWITCH OFF ,Press POWER UP+ for 12sec
Reconnect to the comp ,now your DEVICE MANAGER will show your port ENTRY as QUALCOMM HS-USB MSM DIAGNOSTICS
Click on that entry and Click on Properties > Driver >Update >Browse my comp >
Now select the folder in which you have downloaded the Qualcomm drivers x64 or x86 (from the post above ,you should have downloaded them in the beginning).
Now install that , If it asks for an Restart COMP ,RESTART comp( i restarted,just to be safe).
Step 4 : Completion
Connect the phone in fastboot mode(Just the power up+ & connect )
msm.exe > open in admin mode.
Open up the MSM.exe in the folder (the big file that you downloaded earlier the 800MB one )
It will recognize your device,If it doesn't.
Unplug Phone.
Power Off
Power Up+ ,wait 10sec ,and Plug in ,(hold the power up)
MSM.exe will recognise your device, Try to click start on that and see if it triggers it ,else just close and reopen msm.exe
Your device will be recognised Press Start, it'll do the rest.
After all this,a recovery mode will show up,click yes/ no and Continue.
That's all.OnePlus X good as new
arun.
arundp95 said:
Sure.
That's all.OnePlus X good as new
arun.
Click to expand...
Click to collapse
Let's hope someone finds this useful in future. Thanks for the detailed steps to recover the phone.
arundp95 said:
Sure.
As the Post above mentioned (in the first comment) ,thats the way to go to fix a Hard bricked / bootloop stuck / no Display.
But if you encounter any problems or issues like i did (the QualCom 9008 ...).I did these
Note : all downloads for this adventure are already present in that guide ,Give it a thumbs up after you fix it as it just recovered a potato , link
HTML:
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Step 1: Requirements
Download the qualcom drivers,fastboot-adb all of that,even though i had them installed,i did a clean installation.
Download the Huge 800MB file (the Recovery tool).
Unzip them to the Desktop, 2 folders (1 for the Qualcomm driver,another for the msm).
Step 2: Set-up
Follow the turning off drive signature process from the post above ,Its fairly simple(press shift restart,advanced,f7 restart).
Install adb-drivers.
Switch off phone (press Power Button for 12 sec or so )till it vibrates and display is blank.
Press the Power Up button and plug in the Phone to your comp
If your Internet connection is turned on,mostly windows will itself download and install the driver(qualcom-xxx) for this device.
Step 3:
Now Unplug the phone.Switch it off(your display will be blank ,to begin with but remove phone press power button 12 sec (wait for vibrate )
Press power button up and plug it back in the comp.When you do this navigate to the Device manager tab ,A new entry in that table will be present Ports & Coms or so. If you dont have this ,no worries (go back to the First step and try to get your drivers re-Installed) .
Now that you have located your com port, RELINK HS-USB QDLOADER 9008(com3) in my case( you might have anything else ,but getting this is crucial).
On that Entry right click and go to Properties.In properties > Driver Tab > Update Driver
Once you click Update, Click on Browse my comp for driver
Then Click on LET ME PICK FROM A LIST
UNCHECK the SHOW COMPATIBLE HARDWARE // Have to do this !
Under Manufacturer,FIND Qualcomm Incorporated
Under MODEL,Select QUALCOMM HS- USB MSM DIAGNOSTICS xxxx (i chose the first entry,BUT MSM is integral).
Install that .RESTART COMP,IT'll PROMPT.
UNPLUG PHONE ,SWITCH OFF ,Press POWER UP+ for 12sec
Reconnect to the comp ,now your DEVICE MANAGER will show your port ENTRY as QUALCOMM HS-USB MSM DIAGNOSTICS
Click on that entry and Click on Properties > Driver >Update >Browse my comp >
Now select the folder in which you have downloaded the Qualcomm drivers x64 or x86 (from the post above ,you should have downloaded them in the beginning).
Now install that , If it asks for an Restart COMP ,RESTART comp( i restarted,just to be safe).
Step 4 : Completion
Connect the phone in fastboot mode(Just the power up+ & connect )
msm.exe > open in admin mode.
Open up the MSM.exe in the folder (the big file that you downloaded earlier the 800MB one )
It will recognize your device,If it doesn't.
Unplug Phone.
Power Off
Power Up+ ,wait 10sec ,and Plug in ,(hold the power up)
MSM.exe will recognise your device, Try to click start on that and see if it triggers it ,else just close and reopen msm.exe
Your device will be recognised Press Start, it'll do the rest.
After all this,a recovery mode will show up,click yes/ no and Continue.
That's all.OnePlus X good as new
arun.
Click to expand...
Click to collapse
Hi Saurabh40629/ arundp95
that 800mb link may be expired. unable to download the file.could you please share the new link. it'll be really helpful for me.
I am trying to resolve this from last week unable to get that file.
Please Help!!!!!!!
Hi vinesh ,
Did you got the 800mb recovery tool link
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro.
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Example screenshot:
jwoegerbauer said:
@element14
When you enter
Code:
adb devices
and don't see an entry listed under the “List of devices” section, then your device isn't connected to PC.
Same is case when you enter
Code:
fastboot devices
Recovery option "Apply update from USB" isn't equal to "adb sideload". This option assumes the Update.Zip you want to flash is located on USB-device connected with your TV box.
Click to expand...
Click to collapse
I tried to flash a custom script that use the
Code:
u_print()
function , but the signature verification fails i get an
Code:
errorr:21
jwoegerbauer said:
With regards to rooting your TV box you can try to flash Chainfire's SuperSu Pro[/url].
Click to expand...
Click to collapse
Are you sure that I can flash an unsigned zip like superSu , with a stock recovery and locked bootloader ?
jwoegerbauer said:
BTW: TWRP isn't a recovery image you compile in order to flash, it's merely a touch-enabled replacement for device's Stock Recovery menu as shown by you
Click to expand...
Click to collapse
The TWRP is an open source project , all the source code is avaiable. But to have it works , you need the original kernel .
I tought , If I can unlock the bootloader I can read the image of the recvoery.img and from it extarct the kernel
Thanks for your answer.
@ element14
did you manage to make the device usebale?
Hello, i am also interested to reset\flash this device but I couldn't find any useful guide, did you manage to root it or flash it, I want to use it as android STB.
As long as you can establish an USB-connection ( read: ADB connection ) then you can root any device's Android OS, otherwise NOT.
Any updates on this topic? It would be great to know if someone was able to root it.
If this is the etisalat version of this box I have gotten APKs to work on it.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
What apk exactly?what you can do with this apk? And how you installed?
element14 said:
What apk exactly?what you can do with this apk? And how you installed?
Click to expand...
Click to collapse
I think it lets you install any APK on the device. Check https://emiratestel.github.io/website
There is only one port. Is there any other way? And how can i play videos from usb
xilogofficial said:
I think it lets you install any APK on the device. My method:
Going to apps list:
- insert usb
- click browse
- go up to internal storage, press ok, click Apps
part 1
- go to apps list, keep usb inserted
- scroll to Files, click it, click open
- if it opens skip to part 2
- else it will crash and show the first time boot
- go to apps list again while keeping usb inserted
- open files again
part 2
- connect a mouse to other USB port, navigate into the USB and into where you placed your APKs
- double click the apk to install it
- on first time install, it will show an error about unknown sources
- click settings on the prompt
- enable all sources shown
- continue installing the app
Click to expand...
Click to collapse
There is only one usb port. Is there any other way? And how can i play videos from usb
there's another on the bottom, or use a USB hub.
you can't play videos from USB without installing third party apps.
xilogofficial said:
If this is the etisalat version of this box I have gotten APKs to work on it.
Click to expand...
Click to collapse
Good Day! Appreciate your support . Dear Exactly Etisalat TV box model: DWI259S, but it is locked on Etisalat home page with their logo as I don't have Etisalat subscription any more, in that situation how possible to browse an APK file as you said in below steps? 2nd thing there is no standard Firmware available by Manufacturer (Technicolor), Please make a video or at least solve with help of photos and help us close this topic. Till date solution is not yet provided, Please help, Thanks and appreciate your support
.
element14 said:
Hi guys, I'm here to learn something about Android Security System.
I have this Sapphire TV BOX
model: DWI259S / UIW4020ETI / UIW4020ETI2 (Sapphire)
SoC: Broadcom BCM7271
The goal of this post is to understand how I can gain root access on this device
I know how to turn it in recovery mode .
if you are interested you can read this Reddit post from ams_sharif
"You can boot to recovery by switching the unit off ( the black button in the back), then while holding the power button (the one on the side, next to the pair button) turn the set top box on until the recovery shows up."
This is what I see.
I tried to flash an update.zip in order to see if I can execute command through any script, but the verification of the signature fails.
I tried to click on "Apply update from USB" (that is adb sideload) , but connecting the tv box on the pc nothing happen, no device found neither with "adb devices"
I tried also to click on "Reboot to bootloader" but "fastboot devices" command return nod devices connected.
My idea was to read the recovery image from fastboot extract it and try to compile my own TWRP
Do you have any suggestions to guide me in the right way?
Click to expand...
Click to collapse
Any Luck dear, Please advise as I want the same solution and receive same error 21.
engr.sys said:
Any Luck dear, Please advise as I want the same solution and receive same error 21.
Click to expand...
Click to collapse
Kindly Join our Discord Server Link :https://discord.gg/sbFnauNTWy
I can help u there
Hi
Can you please share the APK please ?
any update on this? did anyone managed to finally root this device or least sideload and apk?
b1acktiger said:
Hi
Can you please share the APK please ?
Click to expand...
Click to collapse
PM Me
Can you please share the APK please ?