I keep getting error 7 in twrp when flashing roms - E 2015 Q&A, Help & Troubleshooting

Just as the title says, I get this error when I flash cm13 Roms. I don't know if it is a bug with twrp or something actually wrong with my device. The only rom that I can flash is cypher for reason.
{
"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 don't know what to do.
Sent from my XT1526 using XDA-Developers mobile app

Download Minimal ADB and Fastboot, unzip to Desktop: http://forum.xda-developers.com/showthread.php?t=2317790
Reboot Moto E into bootloader mode, connect to PC.
Open a command prompt to the unzipped Minimal ADB and Fastboot folder.
Type (I'm assuming you're on Boost, given your forum carrier avatar): fastboot oem config fsg-id boost
Should only take a second to config, then disconnect and reboot the phone back into the bootloader, then go to recovery and try flashing CM13 again.

xtermmin said:
Download Minimal ADB and Fastboot, unzip to Desktop: http://forum.xda-developers.com/showthread.php?t=2317790
Reboot Moto E into bootloader mode, connect to PC.
Open a command prompt to the unzipped Minimal ADB and Fastboot folder.
Type (I'm assuming you're on Boost, given your forum carrier avatar): fastboot oem config fsg-id boost
Should only take a second to config, then disconnect and reboot the phone back into the bootloader, then go to recovery and try flashing CM13 again.
Click to expand...
Click to collapse
That worked thanks
Sent from my XT1526 using XDA-Developers mobile app

Have similar issue on Xiaomi Mi5. Not familiar with the command you're talking about but wonder if it would work there... can you explain what this minimal fastboot deal is? The only other solution I've found is delete the code that prevents flashing a rom for a diff device & hardbricking... which I don't wanna risk. Thanks for any help you can offer.

fourth1 said:
Have similar issue on Xiaomi Mi5. Not familiar with the command you're talking about but wonder if it would work there... can you explain what this minimal fastboot deal is? The only other solution I've found is delete the code that prevents flashing a rom for a diff device & hardbricking... which I don't wanna risk. Thanks for any help you can offer.
Click to expand...
Click to collapse
Can you post a screenshot of the error so I'll know exactly which one you're getting? I don't want to give you the wrong information.

Android_noob17 said:
Can you post a screenshot of the error so I'll know exactly which one you're getting? I don't want to give you the wrong information.
Click to expand...
Click to collapse
Well, I'm afraid not, but for the happy reason that it was fixed by flashing yet another ROM and checking all the options in TWRP manager to backup & wipe before flashing. Not sure if it was that I found the right ROM (screenshotted below) finally or that I should've been wiping while flashing in a single step like that (also screenshotted)

I too getting same problem ,how to solve

shiva sai teja said:
I too getting same problem ,how to solve
Click to expand...
Click to collapse
Just follow the instructions given by @xtermmin, the process is simple.

Related

No Wifi No Data on AOSP roms READ THIS BEFORE POSTING!!!

You need three things besides your phone:
You lost data/wifi when flashing a CM UPDATE, this is your fault for not reading the threads, The FIX IS BELOW, in simple, plain english, easy to understand. DON'T MAKE ME DRAW PICTURES
1) Android SDK
https://developer.an.../sdk/index.html
Download it and install it. I'll only describe it for Windows OS.
2) The correct ROM
https://download.cya.../?device=enrc2b
or from my CM-12.1/AOSP threads
Download it and open it with WinRAR or Winzip or just unpack the whole thing. Directly in the root folder you'll see a file called boot.img
3) USB Cable connection between the phone and your PC
Connect the device to your PC. On your phone go to settings and enable USB debugging.
Now you are ready to flash the boot image.
a) copy the boot.img to the same folder as fastboot
if you downloaded the package from above, you'll see a folder structure that is a bit overwhelming. Navigate to
C:\adt-bundle-windows-x86-20140702\sdk\platform-tools
and copy the file called boot.img from the ROM there.
B) open up the terminal
click on start and enter cmd.exe
enter the folder with
cd /
cd C:\adt-bundle-windows-x86-20140702\sdk\platform-tools
c) start the flashing
Now type:
adb reboot bootloader
or alternatively, restart your phone manually and press the buttons Power and Volume down until you see a white menu screen.
Now type:
fastboot devices
and you should see your phone
d) flash the boot.img
type:
fastboot flash boot boot.img
That's it, 3G and WiFi should work now. A more extensive How-To can be found here:
http://wiki.cyanogen...l_CM_for_enrc2b
Taken from my thread of the same title from the CM forums
http://forum.cyanogenmod.org/topic/101207-no-wifi-no-data-read-this/
IF YOU CANNOT FOLLOW THOSE SIMPLE INSTRUCTIONS GIVE UP NOW
Hi @Lloir,
as far as i can see you have removed the aosp5.1 thread, right? that means no work from you for one x+ anymore?
now i also see that there is no one x+ in your signature...
mmm...bad news...
is it just because of the newbies and there stupdi questions? the best way to get rid of them is to ingore them!!!
.
el-Loko said:
Hi @Lloir,
as far as i can see you have removed the aosp5.1 thread, right? that means no work from you for one x+ anymore?
now i also see that there is no one x+ in your signature...
mmm...bad news...
.
Click to expand...
Click to collapse
My X+ is dead and I'm now mostly working on Huawei devices.
shhh....ititit :'(
.
{
"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"
}

			
				
Hey,@ Lloir
Ive tried this for my stock ROM that ive reverted to after having cyanogenmod 11, but it didnt work, I used the same boot.img from the firmware.zip. it did work successfully when reverting to cyanogen after it didn't work though.
What have I missed?
Any help would be appreciated.

Bootloader Unlocking

Hello,
I'm trying to unlock the bootloader of my kindle fire Apollo, i'm using this tutorial Link., i'm getting most of it, but this i just dont understand:
download the attachment on the following post: http://forum.xda-developers.com/show...2&postcount=46
Then place the file inside the attachement to C:\Python27 should be C:\Python\cuberHDX.py
Click to expand...
Click to collapse
I've just put the cuberHDX file in my python27 directory, and tried following everything else. I think most of it worked, i've gotten a .unlock file, but when i try to flash it to my device it just says <waiting for device>.
I hope you guys can help me out here...:angel:
HybridLion said:
Hello,
I'm trying to unlock the bootloader of my kindle fire Apollo, i'm using this tutorial Link., i'm getting most of it, but this i just dont understand:
I've just put the cuberHDX file in my python27 directory, and tried following everything else. I think most of it worked, i've gotten a .unlock file, but when i try to flash it to my device it just says <waiting for device>.
I hope you guys can help me out here...:angel:
Click to expand...
Click to collapse
Try these drivers. Might require reboot and/or dis- and re-connection of the HDX. Worked for me right away though.
Cl4ncy said:
Try these drivers. Might require reboot and/or dis- and re-connection of the HDX. Worked for me right away though.
Click to expand...
Click to collapse
THANK YOU!
This is a giant leap forward, now my device actually shows up in fastboot. But when i try to flash the .unlock file it says:
{
"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"
}
any idea's?
btw my kindle says: "getvarartition-type:unlock...Ok."
You must change dir (cd) to your ADB Directory, enter cd\adb and then the fastboot command.
Alternatively you can try to add the path of your ADB Directory to the .unlock file, e.g. c:\adb\0x155.....unlock.
Cl4ncy said:
You must change dir (cd) to your ADB Directory, enter cd\adb and then the fastboot command.
Alternatively you can try to add the path of your ADB Directory to the .unlock file, e.g. c:\adb\0x155.....unlock.
Click to expand...
Click to collapse
You Sir are amazing!
Now i'm going to have to install some sort of recovery... i was thinking of using this one: http://forum.xda-developers.com/kin...ecovery-twrp-recovery-2-8-1-0-apollo-t2991155, are there any alternatives or better options?
TWRP is the best you can get for the HDX.
HybridLion said:
You Sir are amazing!
Now i'm going to have to install some sort of recovery... i was thinking of using this one: http://forum.xda-developers.com/kin...ecovery-twrp-recovery-2-8-1-0-apollo-t2991155, are there any alternatives or better options?
Click to expand...
Click to collapse
You can only install a recovery that has been customized for your device type (HDX Apollo or Thor). Any other will either leave you with a non-functioning recovery (best case) or a useless brick (more likely). Word to the wise: don't deviate from the script when messing with an HDX. Hard to tame and nearly impossible to recover. Standard bag of 'android' recovery tricks (eg: factory cables, fastboot, etc) won't work with this device.

Can't flash any Rom - "assert failed: oppo.very_trustzone ERROR 7"

I'm currently on CM 13.0-20160809-NIGHTLY-onyx and I've tried to flash three different Roms on my phone (Two different versions of cm14 and OOS3) with TWRP. But every time I get the error message attached in the screenshot.
Now, I've seen a few people online having similar problems, but it was mostly for cm12 and the suggested fixes are not really helpful for my situation.
I've somehow lost my stock backup so I'm kinda lost right here.
{
"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"
}
In general Error 7 usually means you're using the wrong version of TWRP. I'm still using Blu_Sparks version for the new bootloader.
quoakkaflocka said:
I'm currently on CM 13.0-20160809-NIGHTLY-onyx and I've tried to flash three different Roms on my phone (Two different versions of cm14 and OOS3) with TWRP. But every time I get the error message attached in the screenshot.
Now, I've seen a few people online having similar problems, but it was mostly for cm12 and the suggested fixes are not really helpful for my situation.
I've somehow lost my stock backup so I'm kinda lost right here.
Click to expand...
Click to collapse
You need to upgrade your bootloader and TWRP.you are using very old CM and now everything is changed so upgrade your boot loader and recovery.
I already use TWRP 3.0.2-0 which is the newest version according to TWRP Manager.
How do I upgrade my bootloader?
Edit: So I found this way to do it :Link
The thing is: it says the bootloader must be unlocked, but if I type "fastboot devices" I get nothing back. "adb devices works. I'm pretty sure that my bootloader is unlocked since I have a custom rom and my device is rooted but I'm not sure if I have activated the CM recovery option in the developer settings ever since.
I really don't wanna brick my phone so I'm not sure if I should blindly follow the steps in the link above.
quoakkaflocka said:
I already use TWRP 3.0.2-0 which is the newest version according to TWRP Manager.
How do I upgrade my bootloader?
Edit: So I found this way to do it :Link
The thing is: it says the bootloader must be unlocked, but if I type "fastboot devices" I get nothing back. "adb devices works. I'm pretty sure that my bootloader is unlocked since I have a custom rom and my device is rooted but I'm not sure if I have activated the CM recovery option in the developer settings ever since.
I really don't wanna brick my phone so I'm not sure if I should blindly follow the steps in the link above.
Click to expand...
Click to collapse
"fastboot devices" doesn't work unless you are in the bootloader

I want to install a costum rom, but I have problems with rooting and twrp installing

Hey,
I want to install a costum rom to get a free of bloatware system, but I have problems with rooting my device and installing TWRP. I tried some tutorials today, but none worked for the same reason. For example this one: https://forum.xda-developers.com/m4-aqua/general/root-t3421932 I have a e2303 so I downloaded the e2303 file and went into the adb folder opened cmd connected my phone with pc while I pressed volume down. after that I copy pasted the command "fastboot devices" but it didn't show me any phone, so I went to the next step and copy pasted the command "fastboot flash recovery recovery.img" , but cmd only said <waiting devices>, so I did that what a different guide said (connecting the phone with volume up), but even that didn't worked. I installed adb with adb setup 1.4.3 and answered every question with "y".
I unlocked the bootloader with Flashtool, and it worked. I even relocked and unlocked the phone again.
My phone is a E2303 with build number 26.3.A.1.33 on android 6.0.1, which should be marshmallow.
That is the adb folder where I tried it:
{
"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 really hope that have an idea to help me <3
(picture if that is not working: https://picload.org/view/rpwdarpa/adb.png.html
update: https://www.youtube.com/watch?v=nQjg6ePnGAc this tutorial fixed my problem
You forgot to install ADB and Fastboot drivers }:->
Gray47Maxx said:
You forgot to install ADB and Fastboot drivers }:->
Click to expand...
Click to collapse
yeah, I used that tool but the phone didn't use the drivers automatically. which rom has the fewest bugs and no bloatware and is optimized?
GamingAori said:
yeah, I used that tool but the phone didn't use the drivers automatically. which rom has the fewest bugs and no bloatware and is optimized?
Click to expand...
Click to collapse
No one. But you can install stock, root it, install one of the bloatware-deleting scripts (I can provide you one), install SMK and then it'll be fine )))
Gray47Maxx said:
No one. But you can install stock, root it, install one of the bloatware-deleting scripts (I can provide you one), install SMK and then it'll be fine )))
Click to expand...
Click to collapse
yeah then I'm interested in a bloatware delecting script.
GamingAori said:
yeah then I'm interested in a bloatware delecting script.
Click to expand...
Click to collapse
Sorry for the delay >:^)
View attachment ClearModv2.zip

Question Potential Hard Brick after attempted TWRP Flash

Followed the Unofficial TWRP link, this one https://forum.xda-developers.com/t/...215-twrp-for-sony-xperia-1-iii.4515465/unread
TWRP didn't flash to slot b, and like an idiot I thought, "well let's just do a and see if that works..."
It didn't work, and now only getting a blinking red light when connected to power and computer. No amount of trying to go in to fastboot, bootloader, recovery works. Newflasher, XperiaCompanion, and Emma are not showing anything. I saw this post, and wondering if I've actually managed to brick it beyond repair https://forum.xda-developers.com/t/how-to-save-a-black-brick.4426071/post-86959167
Please help. Any and all feedback welcome!
Thank you!
smmate3 said:
Followed the Unofficial TWRP link, this one https://forum.xda-developers.com/t/...215-twrp-for-sony-xperia-1-iii.4515465/unread
TWRP didn't flash to slot b, and like an idiot I thought, "well let's just do a and see if that works..."
It didn't work, and now only getting a blinking red light when connected to power and computer. No amount of trying to go in to fastboot, bootloader, recovery works. Newflasher, XperiaCompanion, and Emma are not showing anything. I saw this post, and wondering if I've actually managed to brick it beyond repair https://forum.xda-developers.com/t/how-to-save-a-black-brick.4426071/post-86959167
Please help. Any and all feedback welcome!
Thank you!
Click to expand...
Click to collapse
Where did you have the twrp file saved? I personally save any file I flash to my phone in the same directory as Platform Tools/ADB Fastboot install...that way I don't have to add the path location to the terminal command line.
Ainz_Ooal_Gown said:
Where did you have the twrp file saved? I personally save any file I flash to my phone in the same directory as Platform Tools/ADB Fastboot install...that way I don't have to add the path location to the terminal command line.
Click to expand...
Click to collapse
It was saved in the platform tools folder with all the necessary files
smmate3 said:
It was saved in the platform tools and ADB folder
Click to expand...
Click to collapse
Okay well that rules out the possibility of flashing the wrong file..
Ainz_Ooal_Gown said:
Okay well that rules out the possibility of flashing the wrong file..
Click to expand...
Click to collapse
I made sure I was downloading the correct TWRP file for the 1 III, updated platform tools to the current version, renamed the img to twrp.img, attempted to flash, and now just getting the notification led blinking red
Here is everything I did- let me know if I messed up somewhere
{
"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"
}
Ainz_Ooal_Gown said:
Okay well that rules out the possibility of flashing the wrong file..
Click to expand...
Click to collapse

Categories

Resources