Hi Everyone,
So i tried a installing the latest version of Xposed x86 and got my Dell 7840 bricked.
It's running the latest 5.1 OS (Nov 2015 update), but is NOT OEM unlocked ( I can't for the hell of me figure out how it is bootloader locked and rooted! ).
It does not have custom recovery, only stock recovery so i can only do ADB sideload but not update from zip?
I can get to the fastboot menu, but i can't do the tethered recovery as everything failed due to locked bootloader.
i can't unlock the bootloader via fastboot as i can't boot to the OS due to stuck at the Intel inside bootscreen.
When i goto the covery mode. i see "Venue 8 7840-user 5.1 LMY47I BBP803A173600DEL release-keys"
I tried to use the Intel Platform flash tools to flash DD0_BB.xml as per some unbricking guide, but this seems to only work if you are in the OS and not in the fastboot mode.
Any help will be greatly appreciated! Thanks!
i managed to get the flash to work and got into tethered CWM and flashed a brand new system, all is well, thanks!
phibersg said:
i managed to get the flash to work and got into tethered CWM and flashed a brand new system, all is well, thanks!
Click to expand...
Click to collapse
I have the same problem, you were facing, except I cant even get into recovery....
Do you remember how you solved it?
Hey,
download bootloader and firmware (e.g. https://docs.google.com/uc?id=0B0hcxOtcOlhLdTJzbDhiNFhfTEk&export=download) and flash 5.0.1 fastboot.
Then use FBRL to reinstall the system.
Related
Hi!
I want to get rid of emotion ui on the Huawei. It's rooted, but the bootloader is NOT unlocked. How do i install a custom recovery lik twrp or cwm, and then install the Paranoid Android ROM? I am using a mac.
Thanks!
Unlock the Bootloader
To unlock the boot loader refer to this post:
http://forum.xda-developers.com/showthread.php?t=2666116
it worked for me :angel:
as for the ADB and Fastboot tools, may be this helps:
http://forum.xda-developers.com/showthread.php?t=1917237
i am not a mac user so I have not tried this
... as for installing a custom recovery & roms I am still having trouble with that
Hello good people of XDA.
I have managed to get my HDX stuck in a bootloop by trying to install CM11 for safestrap 4 whilst running safestrap 3.75 and am hoping someone can help me unbrick it
- Was running update-kindle-13.3.2.4_user_324002120.bin rooted with Safestrap-Thor-3.75-os3.2.4-B02 installed
- Attempted to install [ROM] [STABLE] CM-11 for Safestrap v4 2015/07/26 on stock ROM slot from within safestrap. All appeared to install OK
- Upon reboot NO SAFESTRAP and does not go past grey kindle fire logo (no animation)
- Device reboots after 40 seconds
- After much faffing around with drivers I DO have adb access (for 40 seconds until device reboots) and can send adb reboot bootloader to the device to get fastboot. Fastboot commands work and device does not reboot when in fastboot
- Can get to stock recovery if i issue adb reboot recovery or power+vol up
- I (foolishly I now realise) did do a "reset to factory defaults" at the stock recovery
- Unsure if I still have root - dont think so though due to doing factory reset
- Cannot flash a system update because the file is 849mb and the device reboots before the transfer is complete and I get a "protocol error". Also possible lack of root may cause this not to work even if i could copy it across
- Tried to flash signed-thor-twrp-2870.img but got FAILED (remote: flashing not allowed for locked hw) when trying to copy to the SDCard
Looks like I have managed to overwrite the safestrap recovery and for whatever reason the CM11 ROM is not loading.
As I understand it, the general process for unbricking a device is:
- get fastboot access [OK]
- flash a recovery [HELP stuck on this]
- Install a ROM from recovery [will be ok with this once I get a recovery working]
I THINK I need to unlock the bootloader so that I can flash a recovery image but I need root to do that which I think I have lost. Is there a way to check? Is there a way to get root back from adb/fastboot? I have tried KFHDX Toolkit to root the device but get "Kindle Fire HDX 7 (cm_thor-userdebug 4.4.4 KTU84Q 8680464d7c test-keys) is not supported" so it is seems to be recognising it as CM11?
I would really appreciate any guidance anyone could give me
Why didn't you read first and ask first before you did all that?
It says CM11 for Safestrap v4! You did NOT have v4! You can NOT install TWRP on 3.2.4, you Need 3.10 - 3.2.3.2 for this. And I don't think you can unlock the 3.2.4 bootloader either.
This looks very bad for you.
So you should have downgraded to 3.2.3.2, install TWRP, unlock bootloader, and flash CM11. Now it seems you don't have a working system anymore.
Cl4ncy said:
Why didn't you read first and ask first before you did all that?
It says CM11 for Safestrap v4! You did NOT have v4! You can NOT install TWRP on 3.2.4, you Need 3.10 - 3.2.3.2 for this. And I don't think you can unlock the 3.2.4 bootloader either.
This looks very bad for you.
So you should have downgraded to 3.2.3.2, install TWRP, unlock bootloader, and flash CM11. Now it seems you don't have a working system anymore.
Click to expand...
Click to collapse
Yeah I realise all of this now. Thought safestrap would protect me if there was a problem.
So, anyone know if there is anything I can do to salvage my device? Was hoping I would be OK since I have fastboot.....
stragen001 said:
Yeah I realise all of this now. Thought safestrap would protect me if there was a problem.
So, anyone know if there is anything I can do to salvage my device? Was hoping I would be OK since I have fastboot.....
Click to expand...
Click to collapse
Amazon's neutered fastboot environment is useless with a locked bootloader (and next to useless when unlocked). "Factory cables" are totally ineffective on an HDX. You can not unlock your bootloader without downgrading which is impossible without a working system AND functioning recovery. There is an outside chance you might be able to root using HDX toolkit (look for it in the Android Development forum) but not sure what that will accomplish given your device is fully borked. You can not flash a new rom with locked bootloader. You can not flash a 'real' recovery with a locked bootloader or bootloader version vunerable to the signature exploit (3.2.4 is not). Ditto for the bootloader itself. I could go on but the point should be obvious.
I don't know if anyone will respond. I successfully unlocked bootloader via tool and flashed TWRP 2.8+
But I think the problem is that I didn't know which JB bootloader I was using and just tried to flash via instructions from KatKiss 5.1.1 v30 because I've been flashing since Nexus one days and thought it would be the same (I'm stupid). Anyway I somehow managed to flash a different ROM but now stuck on a boot loop and obviously can't get access to Asus stock OS. KatshMallow 6.0.1 still loaded on the tablet with gapps but that won't boot up either.
I tried to adb sideload CM12.1 but it failed. Anyone know how I can get any stable ROM up and running with just using TWRP or adb sideload?
Thanks in advance
When it's starts up can you see which bootloader you're on now?
NP
What do you succeed to do following my tutorial ?
http://forum.xda-developers.com/tra...uide-tutorial-asus-transformer-prime-t3486237
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!
Hii, can someone help me I have this old phone where I am trying to learn how to port roms and port recoveries,but I cant unlock bootloader of it couse I cant get into fastboot, when I press keys on screen shows this
Boot into fastboot
Disable fastboot in shipping
Rebooting in 5 seconds
And like that every time, can someone help, I can get into official rom and have twrp recovery for it, but I dont have fastboot and cant unlock bootloader to boot gsi rom
Its android 8.0 if it helps, or is there a flashable zip for unlocking bootloader?Or any way to reinstall fastboot or make changes in system to unlock bootloader?
Thanks.
Nevermind, i updated device firmware and fastboot is working
(UPDATE) Succefully booted official AOSP android 10
If anyone have this phone and wants android 10 on it I can help him, I have ported TWRP recovery for it and it works
Darijohribi said:
Nevermind, i updated device firmware and fastboot is working
(UPDATE) Succefully booted official AOSP android 10
If anyone have this phone and wants android 10 on it I can help him, I have ported TWRP recovery for it and it works
Click to expand...
Click to collapse
Hi, could you kindly pass me TWRP?
I'm trying on Wiko View 2 Pro but I can't find one that works well
what other experiments did you do on?
I would like to try porting UBPorts
thank you