Related
So yeah I accidentally wiped my partitions as if I were installing a rom. Am I screwed until I get to a pc?
P.s. Out of all days to delete my backup rom file ?
Just set it to boot loader mode and flash stock images...I'm sure there's a tutorial on how to do it..I have the program installed on my computer ready for any time I brick my phone lol but I don't remember the name of the program right now
Edit: heres the link to the method I use http://forum.xda-developers.com/showthread.php?t=3258493
I'm assuming the OP doesn't have a PC due to the last statement he made. I would say yes, nothing you can do until you can get to a PC and flash stock images via Fastboot. Unless you have a ROM zip on your phone that is....which I'm assuming you don't.
You're kinda stuck, you need a PC to flash the factory images. TWRP can't flash OTA's anyway, so don't try that again either. I'd strongly recommend not using a toolkit to flash the factory images too. I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Snakielols1984 said:
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Click to expand...
Click to collapse
Can fastboot see your device when you're in bootloader?
Yes fastboot is able to reconize my device.
Snakielols1984 said:
Yes fastboot is able to reconize my device.
Click to expand...
Click to collapse
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
I've actually tried flashing stock images but every time I tried to run fastboot command I get these errors, "command not found" and I believe the other erro is "file path not found". There's another error that I can't remember off the top of my head what it. When I get home I'll try to run the commands again and see what errors I get
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
elfrosto said:
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
Click to expand...
Click to collapse
on another note I have not flashed Android N OTA. I downloaded that and install via OTA.
wrong thread
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Snakielols1984 said:
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Click to expand...
Click to collapse
What bootloader version are you on currently? Although updated bootloader is recommend, you should be able to skip this step without any issues.
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Snakielols1984 said:
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Click to expand...
Click to collapse
Please post the entire command you are using, as written in your terminal prompt. "No command" sounds like an unrecognized command is being issued. We must use ./ in addition to the fastboot or adb command in order for OSX to execute the action. If following Heisenberg's guide for fastboot, the lone change you need to make for OSX is:
./fastboot devices
./fastboot flash
./fastboot reboot
./ADB devices
Try this out and post your results.
Sent from my Nexus 5X using Tapatalk
Just throwing this out there, it is possible to flash an OTA in TWRP. You still need a PC but its do-able.... I flashed Android N Final to my 6P yesterday by copying the OTA zip (uploaded thanks to another member) to SD, Wiped device as I normally would with any other ROM (left SD intact obviously), Flashed OTA ZIP, rebooted straight to bootloader after flash, fastboot erase boot, fastboot erase recovery, fastboot flashed DECRYPTED BOOT.img (which can be found easily), fastboot flashed TWRP 3.0.2-1 (version just released for N), fastboot format userdata, fastboot format cache, reboot from bootloader directly into TWRP, flashed superSU 2.74, reboot system..... Phone runs beautifully. Not a single issue. Entire process from start to finish was less than 10 minutes.
Its not the most practical route but it does indeed work. OTA just hes to contain the entire Image. I should also mention that this was a jump from a Marshmallow based rom (RR) so you don't have to be on an N preview in order to do this....
Moderators could not provide any evidence
I believe this is why the bootloader is locked is my phone. The cid says it's a Verizon but it's also a project fi and carrier unlocked Google Pixel XL. Is there anyway to modify the boot image so it's RO.BOOT.FLASH.LOCKED=0 I believe that will unlock the bootloader if there was just a way to modify it so you could sideload the modified boot through stock kinda like how you could modify the boot images of Samsung devices and flash them in Odin through the stock bootloader. Any thoughts.
Who would be interested in trying this I modified the boot image in the ramdisk so you can turn oem unlock on and unlock the bootloader.. I didn't want to jump to link posting I wanna see who is interested. You have to sideload the boot image through the bootloader but it installs like it's official.. 32 gb pixel XL only this is the 8.1 dev preview boot image so you need to have 8.1 installed.
Links removed due to suspicious moderator activity and possible tampering with the links while they had them removed.
I really think a modified stock boot image which can be side loaded through the stock bootloader will solve the problem about the Verizon Google Pixel XL having a locked bootloader cause even if the bootloader is locked like it is now once you unlock it via a modified boot image it opens it up for flashing you wouldn't need some fancy tool which you'd have to run on a computer to unlock it or a oem unlock code you could modify the locked boot image to be the key into the bootloader.
What you thinking? You thinking support could be added for the Verizon Pixels once again I know there was development at one time but due to them patching the tool used to unlock the bootloader it stopped after a while well with this you could bring back development for it
We also wanted to make sure there was no central point of failure, where one industry player could restrict or control the innovations of any other. The result is a full, production-quality operating system for consumer products with source code open for customization and porting.
Google stated that on it's Android open source project right now with the locked bootloaders Verizon is basically restricting and controlling the innovations of how the device could be used and Google doesn't go with that that is why the Google store edition pixels are unlocked so I think setting the example that there's a permanent way to keep the Verizon bootloaders unlocked by modifying the boot images will show Verizon that they need to remove some policy's they have in place cause in the end as customers the old saying is the customer is always right.
Actually now that I think about it I can modify the ramdisk by unpacking the boot image and taking a text editer and going in then you can edit it to say 0 then repack it and flash it via side load i believe that's how you do it. I'm pretty sure I can do that. Doesn't seem too hard to do.
I am also seeing in the cid that there's RO.BOOT.OEM_UNLOCK_SUPPORT=0 it needs to be kept at RO.BOOT.OEM_UNLOCK_SUPPORT_0 I believe and the boot hardware is samsungs
This all started out as a question but I answered my own question. Plus it's nice to have a unlocked bootloader. Cheers.
Did anyone tried to unlock it ?
If you wanna see this cid information for yourself get the app called cid getter from the play store it doesn't have the best reviews but it at least gives you the right cid information and shows you how the bootloader was locked
user-67 said:
If you wanna see this cid information for yourself get the app called cid getter from the play store it doesn't have the best reviews but it at least gives you the right cid information and shows you how the bootloader was locked
Click to expand...
Click to collapse
did you start with an unlocked bootloader and were you also able to sideload the modified boot.img and then able to unlock the bootloader? also, is this on a VZW Pixel or XL?
user-67 said:
I really think a modified stock boot image which can be side loaded through the stock bootloader.....
Click to expand...
Click to collapse
You can't do that if the bootloader is locked.
Mod Message: OP could NOT provide photo/video evidence on it. Proceed at your own risk!
Click to expand...
Click to collapse
Who would be interested in trying this I modified the boot image in the ramdisk so you can turn oem unlock on and unlock the bootloader.. I didn't want to jump to link posting I wanna see who is interested. You have to sideload the boot image through the bootloader but it installs like it's official.. 32 gb pixel XL only this is the 8.1 dev preview boot image so you need to have 8.1 installed.
Never mind here's the link for pixel XL 8.1 dev preview https://drive.google.com/file/d/1ehXD2LVOBoRbs1EDh33nLyw7I0aRyOqH/view?usp=drivesdk
Here's the link for pixel 8.1 dev preview
https://drive.google.com/file/d/19xvVkadK79p6OLx5LePZSRA7V201ortd/view?usp=drivesdk
Here is the link for the pixel 2... 8.1 Dev preview
https://drive.google.com/file/d/1M-sgp33NTrrlS12SY0xLQxrec44ZejJl/view?usp=drivesdk
Bump
If you didn't know the part that controls oem unlocking is in the boot image. You can go crazy trying to break into the actual bootloader partition but you don't need all that.
I have a pixel (not xl) and i curious, if the bootloader is locked how can i sideload the boot.img?
Sideload is the install of a custom image what you have here is a modified custom boot image which install like it's stock so in terms sideload is what it is through the bootloader
When it comes to boot images I'm good at tweaking them here's a old project it was just a test build to see if it would actually work.
Custom adb root boot image with chainfires adbd kernel from adbd insecure as the phones adbd.. it has a few other tweaks and a custom permissive kernel and systemless root from chainfires supersu... the rsa fingerprint doesn't pop up when you connect a computer but it can be bypassed with adb in a custom recovery and found out if you use adbd insecure and let it patch chainfires adbd kernel it makes the phone as attached device in for adb devices instead of the plain unauthorized device and vendor keys not set. ... if you use it now you get adb root access and regular root access with the su binary but due to the rsa fingerprint not popping up you have to use adbd insecure until a recovery comes out cause it bypasses rsa fingerprint.. credits to come... to use adb root access you need a custom recovery with adb... adbd insecure app... adb on you're computer.... android sdk/android studio... java... boost mobile j7 running build f3 but you can just run systemless root until a recovery comes through. You can grab systemless root from here http://forum.xda-developers.com/gala...j700p-t3430185
And use it with the boot image.. but i just added systemless root patches to the boot image so all you have to do is flash the boot image.
user-67 said:
Who would be interested in trying this I modified the boot image in the ramdisk so you can turn oem unlock on and unlock the bootloader.. I didn't want to jump to link posting I wanna see who is interested. You have to sideload the boot image through the bootloader but it installs like it's official.. 32 gb pixel XL only this is the 8.1 dev preview boot image so you need to have 8.1 installed.
Nevermind here's the link https://drive.google.com/file/d/1ehXD2LVOBoRbs1EDh33nLyw7I0aRyOqH/view?usp=drivesdk
Click to expand...
Click to collapse
Will you be able to provide the boot image for Verizon pixel on 8.1? I would be interested in trying it. Thank you.
i definitely want to try this, i have the VZW Pixel, not upgraded to 8.1 yet, but will if this is made available for the pixel!
If you all give me a copy of your boot.img in Img format I'll do the ramdisk changes.. you can get a copy by downloading the factory image you want then on your phone go to the play store and get the app zarchiver then go in and open the factory image and copy the boot image into internal storage then hit the Google drive and post a link and I'll get right on it.
Guys, I'm in trouble. I unlocked my boot loader via Motorola's site. I then tried to install TWRP and then tried to root (SuperSU, I'm really that far behind). I'm really at a loss of words. All I can get is "WARNING BOOTLOADER UNLOCKED" and when holding down volume and power button, I can access what says "START," but when I go back up to "RECOVERY MODE" it goes back to flashing the warning bootloader unlocked. Is there any hope?
I got the 7.0 update, but decided that was the end of the road for the phone and wanted to try out a few ROMs. Right now, I have no idea what sort of mistake I made. Somewhere, I deleted my backup and now I'm stuck with "AP Fastboot Flash Mode (Secure)". If I try to go to recovery it just boot loops. I also tried to install a few ROMs, but they all stop at the loading screen. Please someone help. :crying: It's my fault, I know. Anyone have ideas? Is there anything like Odin, but for Motorola? Any help would be tremendously appreciated.
Flash full stock without relocking bootloader.
https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142 (if you have xt1575 US)
One reboot.
For "WARNING..." you need modified logo.bin.
If you want:
Flash or boot only twrp 3.+(3.2 is newest) and root with magisk14.zip.
---------- Post added at 11:32 PM ---------- Previous post was at 11:31 PM ----------
@Moceimo
I appreciate the help. I just don't understand what the instructions are. How do I go about flashing this zip file? I'm on Windows 10 and the US variant. Do I need a custom recovery on my phone or do I do it from CMD prompt? I've tried Fastboot, but it only let's be install several things which that says to do. Most fail.
Moceimo said:
I appreciate the help. I just don't understand what the instructions are. How do I go about flashing this zip file? I'm on Windows 10 and the US variant. Do I need a custom recovery on my phone or do I do it from CMD prompt? I've tried Fastboot, but it only let's be install several things which that says to do. Most fail.
Click to expand...
Click to collapse
You can use rsd if your win10 can identify it, or use fastboot.
7.0 can be rooted with su282(I used twrp3001).
By the way, if you upgrade 7.0 by OTA, then the system partition size will reduce 2GB, which may affect the 3'rd party roms,and you can't downgrade it to the lower version of the system. If not by OTA or not flash the file gpt of 7.0’s stockrom, then there is no impact.
zi_mo said:
By the way, if you upgrade 7.0 by OTA, then the system partition size will reduce 2GB,...
Click to expand...
Click to collapse
What are you talking about?
My partitions are the same sizes as on MM. System is 4gb.
Xt1572reteu.
Btw. Any chance for RetEu 7.0 image files?
@Moceimo
You need extract zip to minimal adb & fastboot folder. Only .img .bin files you can flash with fastboot.
ROM is still under development.
Downloads
20180427-1610
20181006-1451
XDA:DevDB Information
DOOGEE_X30_AOSP, ROM for all devices (see above for details)
Contributors
ttomovcik, VeteranoX, SoaringLake
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 20181127-1452
Beta Release Date: 2018-11-27
Created 2018-05-24
Last Updated 2018-11-28
Reserved
Reserved
Due to some bugs in TWRP, we recommend to charge your device to AT LEAST 70% and keep the device plugged in. I'm still waiting for DOOGEE to respond (emailed them if they can send the kernel source). So In the meantime, enjoy overheating and quick battery discharge in TWRP.
New build out! This addresses the following bugs:
Camera FC when opening settings
Camera slow-mo not working
Perfrmance issues
Enabled on-screen navbar - hardware buttons will remain enabled, however, changing Generic.kl will result in HW buttons not working
Changelog
20181018-1337 (Created by SoaringLake)
[FIX] Missing launcher
[ADDED] Face recognition
20181006
Removed Gallery2 - caused problems, needs to be replaced with GApps
Added sqlite3
Taking screenshots now works
20180427-1610
Initial release
Features / what's working
GPS
Phone calls / mobile data
Wi-Fi
DuraSpeed
Brightness (can be adjusted lower than stock)
Volume changing works (stock ROM doesn't have this for some reason)
Youtube supports VR
MiraVision
Bugs / feature requests
Settings > about phone is showing some random indian guy as maintainer. This is due to the fact that this ROM is ported from another device to X30. Will fix that later, probably
When quickboot is active, phone will charge when off without the charging screen animation
NVRAM ERROR is showing in Wi-Fi networks
Google Play services not updating automatically
Unable to open Google Assistant, opens up multitasking view instead
Split screen buggy
No mediatek gestures
Instagram videos rendering incorrectly (SoaringLake)
Camera FC when going to settings
FM Radio volume issues
Camera slow-mo not working
Installation
Unlock bootloader and flash TWRP/CWM (1)
Flash ROM and GApps in one go. DO NOT REBOOT BETWEEN ZIP FLASHING (2)
Wipe cache
Reboot
(1) - Installing TWRP
Enable OEM unlocking in developer options
Download TWRP from here
Reboot into bootloader (Power off and then power on while holding volumeUp)
On your PC, flash it with: "fastboot flash recovery <filename>.img"
Reboot into recovery (Power off, then Power on while holding VolumeUp and select Recovery)
(2) - Flashing ZIP images
Make sure to wipe device
Flash the ROM from device or SD card. Sideload will result in no OS installed error
(Optional) Flash any variant of openGapps - ARM/7.1.1
thread closed until the download links will be available @ttomovcik pm us when you`re ready to share the links
-=-=-
thread re-opened
How can I root?
Hey can you publish the instructions about to root and install Twrp?
And thanks for your work.
mediafire.com/file/3zifgay1h0c334g/TWRP%20dogee%20x30.rar
install via fastboot "fastboot flash recovery recovery.img", only remember to unlock bootloader 1. in developer options> allow OEM unlock 2. In fastboot "fastboot OEM unlock"
the first result on google after entering doogee x30 root
I'm Stuck!
I followed the steps but I got stuck in TWRP with the ROM and without the ROM that I do?
VeteranoX said:
I followed the steps but I got stuck in TWRP with the ROM and without the ROM that I do?
Click to expand...
Click to collapse
When it comes to our Rom you have to do wipe all and then install it because otherwise it likes to make mistakes, I have no problem.
PS. You can enter the twrp and use the recovery, because some img recovery that I liked liked to brick the phone
PS2. At the time of bootloader unblocking, Start the phone again because it has to restore the phone to the factory, Sam so zeged the phone because I did not read the messages on it and immediately uploaded twrp by which he had a bootloop
SoaringLake said:
When it comes to our Rom you have to do wipe all and then install it because otherwise it likes to make mistakes, I have no problem.
PS. You can enter the twrp and use the recovery, because some img recovery that I liked liked to brick the phone
PS2. At the time of bootloader unblocking, Start the phone again because it has to restore the phone to the factory, Sam so zeged the phone because I did not read the messages on it and immediately uploaded twrp by which he had a bootloop
Click to expand...
Click to collapse
Hey can you send me a copy of your stock recovery? Because now i can't turn it on just flastboot.
VeteranoX said:
Hey can you send me a copy of your stock recovery? Because now i can't turn it on just flastboot.
Click to expand...
Click to collapse
Shutdown device, press vol+ and power Button , you will see the menu, vol + you choose the option and vol-approve
and stock recovery I will send it later
recovery: mega.nz/#!raBW3CBC!LLQYl5tZEFyttQg8LWYeqdqu7sKusOUZXxEsHJthNdo
Phliz Touch recovery 6.59.0
for those willing to give a link to philz touch recovery in version 6.59.0, I worked on ClockWokMod but can not see the external sd card
mega.nz/#!PbpHlbjR!VfIomQYwPQQ6f5-1mT7tIF3x66X692rcBiYUQeusLto
I got it!
It was not necessary at the end I downloaded the stock and it was only discharged , but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
---------- Post added at 04:38 PM ---------- Previous post was at 04:25 PM ----------
SoaringLake said:
Shutdown device, press vol+ and power Button , you will see the menu, vol + you choose the option and vol-approve
and stock recovery I will send it later
recovery: mega.nz/#!raBW3CBC!LLQYl5tZEFyttQg8LWYeqdqu7sKusOUZXxEsHJthNdo
Click to expand...
Click to collapse
It was not necessary at the end I downloaded the stock and it was only discharged, but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
VeteranoX said:
It was not necessary at the end I downloaded the stock and it was only discharged , but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
---------- Post added at 04:38 PM ---------- Previous post was at 04:25 PM ----------
It was not necessary at the end I downloaded the stock and it was only discharged, but could you repeat the installation of the TWRP in more detail? I'm also not a natural English speaker.
Click to expand...
Click to collapse
1. go to the developer options in the system, select allow OEM unlock and debug usb.
2, issue the command in ADB "adb reboot-bootloader"
3. issue the command "fastboot oem unlock"
4. restart the "Fastboot reboot" phone
5. allow for wipe data,
6. go to fastboot,
7. issue the command "fastboot flash recovery $ image"
$ image = name with the extension image recovery
I got it!
Hey now is workin (rom and root) i'm testing now and i will send a feedback later but now just i can say
Faster!
Thank you!
Does anyone know how to fix the error: NVRAM WARRNING: Err 0x02
At first to downgrade my CUK4 Bootloader, is there any Option? I've heard that to flash TWRP like there is a easy How-to-do-Guide, I need to have the Bootloader of maximum Level 2 not the actuell Bootloader of Level 4.
So can I downgrade it and when it is possible, how can I do it.
Otherway are there other options to install a TWRP-Recovery, or maybe PitchBlack, or Orange Fox Recovery?
What is the relation ship between my Model ( SM-T295 ) and at first the T290, or further the T280, or T285 ?
There are Lineage ROM's and shurly TWRP written for them. Can I modfify such a Recovery, or ROM to flash it on my T295, maybe, or can you tell me something else, knowables, interesting facts?
These two pictures will show you all informations you need, if you wanna help;
Here are all of my Informations:
Hi, I have been trying to root recently but there are issues I overcome, my bootloader is unlocked the device name is SM-T295, and the build number is T29XXS4CUG4. I gave up on flashing through TWRP because it says that the system is running in unauthorized software so I decided to flash using fastboot but my device ain't getting detected, I did everything like installing ADB and fastboot driver, and when I check in the device manager Samsung mobile USB CDC composite device help me, please.
@JonnyBoy1984 I have removed the photos from your post because they contain critical information such as your IMEI and device serial number. Remember, this is a public forum; everything you post here is visible on the Internet. Please ensure you remove this information in the future.
Also, when posting large photos, please ensure you either resize them or use a spoiler so you don't overwhelm mobile users.