{
"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"
}
Natesu53 said:
View attachment 5826507View attachment 5826509
Click to expand...
Click to collapse
?????
DrScrad said:
?????
Click to expand...
Click to collapse
Do you have a question
I managed to capture a full ota, and a --diff-incremental ota...
Natesu53 said:
I managed to capture a full ota, and a --diff-incremental ota...
Click to expand...
Click to collapse
well, would youliek to share your capture or you just gonna flaunt it? lol.. and were you able to achieve root and succesful boot thereafter ?
DrScrad said:
well, would youliek to share your capture or you just gonna flaunt it? lol.. and were you able to achieve root and succesful boot thereafter ?
Click to expand...
Click to collapse
Yes sir
I was able to capture ota extract the "payload.bin" get the boot image patched it with magisk app . Then I flashed it using fastboot on the computer.
I booted up the device installed root checker and it worked.
Natesu53 said:
I booted up the device installed root checker and it worked.
Click to expand...
Click to collapse
And this was android 12? I'm assuming you had to disable vbmeta as well yeah?
My only question to you... , but that's why I'm here . Is do you correctly have a nord n20 GN2200, and if so does your device turn on properly. Is it bricked .
DrScrad said:
And this was android 12? I'm assuming you had to disable vbmeta as well yeah?
Click to expand...
Click to collapse
Yes I disabled vbmeta
And yes it was android 12
My OnePlus is booting just fine. How'd you go about capturing that ota BTW
Natesu53 said:
My only question to you... , but that's why I'm here . Is do you correctly have a nord n20 GN2200, and if so does your device turn on properly. Is it bricked .
Click to expand...
Click to collapse
Currently** corrections
Natesu53 said:
Currently** corrections
Click to expand...
Click to collapse
I'm trying to show you but it won't let me post the pics cause too much too process with xda
Natesu53 said:
I'm trying to show you but it won't let me post the pics cause too much too process with xda
Click to expand...
Click to collapse
Hit me up on telegram
Or hell just email me with what you're trying to post
[email protected]
Images
So basically you connect your phone to the computer. Make sure you have automatic updates shutoff. Start downloading the update, but don't download it all the way . Pause it after 15 seconds. Type " adb logcat > ota.txt " without quotation . In you platform tools folder there should be a file called it's.txt open it . In the search type " googleapis " and you will find a httpslink.zip copy it and paste it in your browser it should start downloading. Extract the downloaded file. The payload will be in the extracted folder.
Ota.txt** not it's.txt
I have steps for you on how to extract the payload.bin file with payload_dumper-master... Once you got a capture of your ota
Also I have telegram, but I need to download it.
I sent message on telegram
Platform-tools directory in terminal type that command*
Also I had android 11 at first . I did end up bricking my phone trying to install a unofficial TWRP. I thought I was never get my phone back working then I tried to flash different boot.img . I flashed it with different ppls images. Still nothing. Kept doing research. Flashed it more had a phone that finally turned on , but no wifi .... I flashed the October patch android 11 flashed vbmeta , boot image , system.image system_etc.img . I finally was able to turn on my phone have wifi. I noticed there was a new update . I was just gonna download the update to fully get my phone back to normal, but this was my chance to root it cause all the software lined up . I figured out how to capture ota . I capture the ota to my version of the new update. I downloaded my update for Android 12. I patched the boot.img . BOOM flashed it phone successfully rooted . New update to Android 12 and root.
So my phone is currently rooted on the android 12 , but there is a new update . What I'm trying to figure out is how to update it. It seems you can only get the boot.img with full ota . With be android 11 at first . Android 12 was a full ota. Since I'm on android 12 there is a new update, but it's not a full ota . It's a incremental meaning not all the software is getting modified. I did manage to capture my incremental update , and you'll know it's not a full ota if it's only like 100mb. full ota are like 4gb . So I have the payloads for both updates. I'm trying to combine/extract both payload.bins boot.img combine them together to have a new updated root . My phone is still rooted properly . I would just like to stay up to date.
Natesu53 said:
I'm trying to show you but it won't let me post the pics cause too much too process with xda
Click to expand...
Click to collapse
I could definitely use a copy of the recent OTA mine is soft bricked right now. in the boot_b. in boot_a I flashed twrp to boot, the touchscreen doesnt work so i use my mouse on it.
DrScrad said:
My OnePlus is booting just fine. How'd you go about capturing that ota BTW
Click to expand...
Click to collapse
Start the OTA & then logcat - link will be in there
nam*eerf said:
I could definitely use a copy of the recent OTA mine is soft bricked right now. in the boot_b. in boot_a I flashed twrp to boot, the touchscreen doesnt work so i use my
Click to expand...
Click to collapse
nam*eerf said:
I could definitely use a copy of the recent OTA mine is soft bricked right now. in the boot_b. in boot_a I flashed twrp to boot, the touchscreen doesnt work so i use my mouse on it.
Click to expand...
Click to collapse
Umm what android version are you on , and what model . I could possibly upload the images for you to flash. , But my theory is you have to flash all the images on both slots to get it back working . If you're interested lmk.
Like system.img boot.img vendor.img modem.im ect... All the core images
Yes I believe it is possible. It's like getting a new update. And I have it all extracted from the payload bin. I check Here every so often if anyone interested. Like every image
Gotta flash all them so they all line up
Don't wanna just post anything and someone bricks there phone. But if your phone is already bricked , them it don't hurt to try.
I don’t usually post I just kinda hang back and read but I have an n20 gn2200 that I bricked trying to get rw on the system. I have tried so many combinations of flashing this that and the other that I don’t really know what firmware I’ve downloaded anymore. I know I was on 12 before I crashed the phone and was going to try getting twrp on my slot b partition but haven’t got there. If you have flashable imgs for android 12 I’ll give them a shot. Don’t mind trying it out like you said can’t hurt right
I got you . And the thing about twrp . You gotta flash it to your recover.img. it replaces your recovery. I've flashed it to my boot.img , and that's what bricked my phone.
And Nord doesn't have an official twrp that works. And I'm not seeing any recovery.img partitions.
Once I upload to Google drive . I will upload the link to all the images for download. I just need set my computer down and let them upload it'll take a lil time .
Uploading...
I've managed to figure out how to modify partitions and flash them. Like anyone interested in following along with this new project I'm working on. Like I mounted my_product.img to my computer edited some files deleted the carrier boot animations . If you try to mount it it'll mount, but it won't let you edit or delete files. OnePlus partitions are erofs not ext2, ext3, or ext4. Erofs is a read only file system I've came across this program that converts it to ext2. I was able to mount it I edited some files deleted some files. Flashed it .it flashed without a problem. The original my_product.img was like 300 mb. When it got converted it was like 600mb. So I deleted the carrier boot animations, and it reverted to the OnePlus boot animation. When I deleted the OnePlus boot animation it reverted to a stock android boot animation. And when I use a root explorer on the phone it allows me to create folders delete files. So the my_product which contains the boot animations flashed without a problem. So I did the same thing to system.img it lets me convert it edit files. When I go to flash it. I get an error. " fastboot flash system systemsu.img" the error says " invalid sparse file format at header magic Resizing 'system_a' FAILED (remote: 'not enough space to resize partition')". the original system.img was like 700mb then it changed to 1.5 gb once I converted it. If there is a way to reduce the size of the partition it it'll work . Or if you increase the size available, so you don't get an error.
Related
Restarted the tablet just now and noticed a Dell update. Installed it and, something definitely has improved as the tablet seems much quicker. Ran Antutu and the Ram speed has gone way up. Is it possible Dell has addressed an issue with these tablets? Anyone else get this update?
Yes i did receive this update, it fixed some of the browser issues in chrome.
I can't install the update is just fails mid Install with an Android Caution sign and constantly gives me the OTA Notification.
Maybe it depends on how new your Venue 8 is?
petewr said:
Maybe it depends on how new your Venue 8 is?
Click to expand...
Click to collapse
Mine is the newest 8340 - I think I messed something up but I am not sure how to return to stock as the only fastboot images I could find are rooted ones with disabled OTAs.
Haxxa said:
Mine is the newest 8340 - I think I messed something up but I am not sure how to return to stock as the only fastboot images I could find are rooted ones with disabled OTAs.
Click to expand...
Click to collapse
Were you rooted or stock?
My wifes 8340 was rooted and the updater rebooted and promptly failed. Tablet didn't loose root but something is definitely messed up now. I've not had time to figure out what happened yet.
LinuxTom said:
Were you rooted or stock?
My wifes 8340 was rooted and the updater rebooted and promptly failed. Tablet didn't loose root but something is definitely messed up now. I've not had time to figure out what happened yet.
Click to expand...
Click to collapse
Yes I am rooted but no root apps were used and I unrooted to no avail. So it must be to do with the root process or something it has changed in the system partition. If we had fastboot images it would be easy enough to revert to stock and upgrade...
Haxxa said:
Yes I am rooted but no root apps were used and I unrooted to no avail. So it must be to do with the root process or something it has changed in the system partition. If we had fastboot images it would be easy enough to revert to stock and upgrade...
Click to expand...
Click to collapse
Aren't stock images available on the mykit_batch thread?
LinuxTom said:
Aren't stock images available on the mykit_batch thread?
Click to expand...
Click to collapse
Not for the Dell Venue 8340 (New Version) as far as I can see.
Haxxa said:
Not for the Dell Venue 8340 (New Version) as far as I can see.
Click to expand...
Click to collapse
You all can make your own, that's how those are made.
vampirefo said:
You all can make your own, that's how those are made.
Click to expand...
Click to collapse
Yes would appreciate someone taking the lead on that; I can't with my tablet in its current state... :crying::crying::crying:
Haxxa said:
Yes would appreciate someone taking the lead on that; I can't with my tablet in its current state... :crying::crying::crying:
Click to expand...
Click to collapse
I think someone has http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
quote from post below, I don't have this tablet to confirm, I have 3830, have made my own back ups since day one.
Code:
Stock Build YTP802A128630 Images
Note, unless you are doing development, you won’t need to download the following file. For Developers, here are the stock Android 4.4.4 (not rooted) boot.img, recovery.img, system.img.gz:
Dell_venue8_3840_4.4.4_Stock_Images.zip 822.1MB md5sum: 995db36a2daa6bd9955e75fa5a14a519
Haxxa said:
Yes would appreciate someone taking the lead on that; I can't with my tablet in its current state... :crying::crying::crying:
Click to expand...
Click to collapse
Looks like OEM 4.4.4 images are at http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427/post57209175#post57209175
LinuxTom said:
Looks like OEM 4.4.4 images are at http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427/post57209175#post57209175
Click to expand...
Click to collapse
vampirefo said:
I think someone has http://forum.xda-developers.com/dell-venue/development/guide-how-to-root-android-4-4-4-dell-t2918427
quote from post below, I don't have this tablet to confirm, I have 3830, have made my own back ups since day one.
Code:
Stock Build YTP802A128630 Images
Note, unless you are doing development, you won’t need to download the following file. For Developers, here are the stock Android 4.4.4 (not rooted) boot.img, recovery.img, system.img.gz:
Dell_venue8_3840_4.4.4_Stock_Images.zip 822.1MB md5sum: 995db36a2daa6bd9955e75fa5a14a519
Click to expand...
Click to collapse
No Dice!
So I have tried everything to return to stock, the stock images provided in the thread refuse to flash with fastboot outputing error 121, It is a big image and gets half way through downloading system.img when this error occurs, I have tired unbricking but it will not detect my device when pressing download button and have tried about every driver available & 3 computers. I tried using CWM temp boot to flash the system.img put inside a update.zip but it did not work and now I am prepared to return the tablet as it will not restore
Any ideas left to help here?
Here's the error when using fastboot-
{
"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"
}
& The xFSTK Flasher gives no error as I can't no matter what I do get it to detect.
I have now spent 20 Hours trying to fix this - I have run through the guide 3 times and used 3 different computers I have no idea what to do?
Haxxa said:
No Dice!
So I have tried everything to return to stock, the stock images provided in the thread refuse to flash with fastboot outputing error 121, It is a big image and gets half way through downloading system.img when this error occurs, I have tired unbricking but it will not detect my device when pressing download button and have tried about every driver available & 3 computers. I tried using CWM temp boot to flash the system.img put inside a update.zip but it did not work and now I am prepared to return the tablet as it will not restore
Any ideas left to help here?
Here's the error when using fastboot-
& The xFSTK Flasher gives no error as I can't no matter what I do get it to detect.
I have now spent 20 Hours trying to fix this - I have run through the guide 3 times and used 3 different computers I have no idea what to do?
Click to expand...
Click to collapse
Well you should be flashing system.img.gz not system.img.
fastboot flash system system.img.gz
as far as recovery you would need to unpack system.img and build a rom to install via CWM.
vampirefo said:
Well you should be flashing system.img.gz not system.img.
fastboot flash system system.img.gz
as far as recovery you would need to unpack system.img and build a rom to install via CWM.
Click to expand...
Click to collapse
My deep apologies I have never flashed a .gz in fastboot before file I just assumed it need to be unachieved and it was compressed for the purpose of size...
I did try to build a Rom however it would not build on my Linux Server for some reason so I gave up on that after a few hours.
vampirefo said:
Well you should be flashing system.img.gz not system.img.
fastboot flash system system.img.gz
as far as recovery you would need to unpack system.img and build a rom to install via CWM.
Click to expand...
Click to collapse
Well I just managed to restore the system image found on the thread on to the tablet however when updating I encounter the same issue with the update failing. Even after flashing system, recovery, boot and wiping data back to original. There should be no trace of root at all....
Haxxa said:
Well I just managed to restore the system image found on the thread on to the tablet however when updating I encounter the same issue with the update failing. Even after flashing system, recovery, boot and wiping data back to original. There should be no trace of root at all....
Click to expand...
Click to collapse
How did you root? What are the errors you get from OTA update?
sent from my kingSing T1 via taptalk
vampirefo said:
How did you root? What are the errors you get from OTA update?
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
Using Tethered Recovery by Social, and the error is half way through installing OTA in Recovery it goes from a loading (Progress bar) to a red caution symbol and then it reboots. Upon boot the version number and details remian the same....
Also should add this is stock without any mods or installed apps (just flashed and went straight to updating) ... root should have disappeared entirely when I flashed system.
Haxxa said:
Using Tethered Recovery by Social, and the error is half way through installing OTA in Recovery it goes from a loading (Progress bar) to a red caution symbol and then it reboots. Upon boot the version number and details remian the same....
Also should add this is stock without any mods or installed apps (just flashed and went straight to updating) ... root should have disappeared entirely when I flashed system.
Click to expand...
Click to collapse
That doesn't help, if I had that tablet, I would run the ota update through my cwn recovery, all failures are recorded so would know what was wrong.
Stock recovery I don't think records failures, without a log can't help you.
sent from my kingSing T1 via taptalk
This is my first post, so I apologize if I am in the wrong section, but I really need help.
After running diferent custom roms on my KIW-L21, I saw the official MM update on the forum, so I restored my TWRP backup of B140 and tried updating but with no luck, so I tried restoring stock B130. Because the force update wouldn't work I flashed the files manually using adb and fastboot and succeded. The problem is that now, when I go to the 'about phone' panel all the informations except for the version number are wrong :
model is unknown
CPU shows quad core 1,2 GHz
RAM 1,0 GB
Memory 4,0 GB
Resolution 540 x 960
Android version 4.3.
Has anyone encountered anything like this?
Once again, I am very sorry if I posted this in the wrong section, but I could really use some help.
cosminvr27 said:
This is my first post, so I apologize if I am in the wrong section, but I really need help.
After running diferent custom roms on my KIW-L21, I saw the official MM update on the forum, so I restored my TWRP backup of B140 and tried updating but with no luck, so I tried restoring stock B130. Because the force update wouldn't work I flashed the files manually using adb and fastboot and succeded. The problem is that now, when I go to the 'about phone' panel all the informations except for the version number are wrong :
model is unknown
CPU shows quad core 1,2 GHz
RAM 1,0 GB
Memory 4,0 GB
Resolution 540 x 960
Android version 4.3.
Has anyone encountered anything like this?
Once again, I am very sorry if I posted this in the wrong section, but I could really use some help.
Click to expand...
Click to collapse
you need this > http://forum.xda-developers.com/honor-5x/how-to/kiw-l21-c432b130-uk-revert-package-t3368480
clsA said:
you need this > http://forum.xda-developers.com/honor-5x/how-to/kiw-l21-c432b130-uk-revert-package-t3368480
Click to expand...
Click to collapse
I already tried that, but at the start of the installation it gives me 'system file instalation failed'.
cosminvr27 said:
I already tried that, but at the start of the installation it gives me 'system file instalation failed'.
Click to expand...
Click to collapse
yeah well where did you get the files you flashed with fastboot ?
use the Huawei Update Extractor and get the files from the link i posted
clsA said:
yeah well where did you get the files you flashed with fastboot ?
use the Huawei Update Extractor and get the files from the link i posted
Click to expand...
Click to collapse
Will try, but after the extraction wich files should I flash?
On a post I saw it said that I should flash only cust, system, recovery and boot.
Is it necesary to flash all the files from the update?
cosminvr27 said:
Will try, but after the extraction wich files should I flash?
On a post I saw it said that I should flash only cust, system, recovery and boot.
Is it necesary to flash all the files from the update?
Click to expand...
Click to collapse
System and data
You may also need cust from paulobrian rom
Sent from my SM-N920C using Tapatalk
clsA said:
System and data
You may also need cust from paulobrian rom
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
I managed to flash a stock rom using gopinaidu77's [RoM][StOcK][Kiw-L22/L21]B140.Debloated, because it is the only one I found that is stock but .zip file.
The only question now, if you can help me with an answer, is what could go wrong if in the 'about phone' panel model number is MSM8916 for arm64 and the file version is kiw-l24c567b140.
I mean, taking to consideration that my phone is KIW-L21 and the original file version it was originally for KIW-L24.
Anyway I really apreciate the help.
cosminvr27 said:
I managed to flash a stock rom using gopinaidu77's [RoM][StOcK][Kiw-L22/L21]B140.Debloated, because it is the only one I found that is stock but .zip file.
The only question now, if you can help me with an answer, is what could go wrong if in the 'about phone' panel model number is MSM8916 for arm64 and the file version is kiw-l24c567b140.
I mean, taking to consideration that my phone is KIW-L21 and the original file version it was originally for KIW-L24.
Anyway I really apreciate the help.
Click to expand...
Click to collapse
this rom contains the /cust partition you need
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
after flashing it with TWRP
Flash stock recovery with TWRP / Install / Install Image >> https://www.androidfilehost.com/?w=files&flid=51004
when you are done leave twrp with power off
now with the update.app files in the sdcard/dload boot the phone with
Power+ vol+ and vol-
EMUI will flash the phone
if you want complete stock boot to stock recovery (power + volume up) and choose factory reset
cosminvr27 said:
I managed to flash a stock rom using gopinaidu77's [RoM][StOcK][Kiw-L22/L21]B140.Debloated, because it is the only one I found that is stock but .zip file.
The only question now, if you can help me with an answer, is what could go wrong if in the 'about phone' panel model number is MSM8916 for arm64 and the file version is kiw-l24c567b140.
I mean, taking to consideration that my phone is KIW-L21 and the original file version it was originally for KIW-L24.
Anyway I really apreciate the help.
Click to expand...
Click to collapse
Download twrp backup for KIW-L21C432B130 from here and restore using twrp
After restoring backup flash stock recovery before booting into system then update as normal through OTA to B140 firmware
https://r.tapatalk.com/shareLink?ur...share_tid=3328288&share_fid=3793&share_type=t
[Repository] The Honor 5x File Depot
Sent from my KIW-L21 using Tapatalk
chubby65 said:
Download twrp backup for KIW-L21C432B130 from here and restore using twrp
After restoring backup flash stock recovery before booting into system then update as normal through OTA to B140 firmware
https://r.tapatalk.com/shareLink?ur...share_tid=3328288&share_fid=3793&share_type=t
[Repository] The Honor 5x File Depot
Click to expand...
Click to collapse
I am sorry guys,it didn't work.
Tried everything but it seems that the only rom working is the one I mentiones above.
Thank you very much,both of You,though,but for now I guess I'll stock to this one.
The only question now remains how will the fact that it show 'KIW-L24' will afect future updates ?
cosminvr27 said:
I am sorry guys,it didn't work.
Tried everything but it seems that the only rom working is the one I mentiones above.
Thank you very much,both of You,though,but for now I guess I'll stock to this one.
The only question now remains how will the fact that it show 'KIW-L24' will afect future updates ?
Click to expand...
Click to collapse
Did you extract the backup from the zip
Sent from my KIW-L21 using Tapatalk
chubby65 said:
Did you extract the backup from the zip
Click to expand...
Click to collapse
Yes I did, the only problem is that it will not boot. It gets stuck at the first honor logo.
It only booted when I tried the first solution but in that case again it was showing 'unknown device' '1 gb of ram' etc.
cosminvr27 said:
I am sorry guys,it didn't work.
Tried everything but it seems that the only rom working is the one I mentiones above.
Thank you very much,both of You,though,but for now I guess I'll stock to this one.
The only question now remains how will the fact that it show 'KIW-L24' will afect future updates ?
Click to expand...
Click to collapse
what didn't work ? if you can't follow simple steps how do you expect to fix the phone ?
Did you download and flash the customromtemplate-5x-plk21-b130-r3.zip from paulobrien ? if you did your phone would not still say L24 it would be L21
The phone boots very slow wait at least 10 - 15 min before you give up on it
clsA said:
what didn't work ? if you can't follow simple steps how do you expect to fix the phone ?
Did you download and flash the customromtemplate-5x-plk21-b130-r3.zip from paulobrien ? if you did your phone would not still say L24 it would be L21
The phone boots very slow wait at least 10 - 15 min before you give up on it
Click to expand...
Click to collapse
I read the description of the rom and saw that it boots slow and left it 35 minute by the watch before giving up. That was the only thing that it didn't work,the fact that it didn't boot.
cosminvr27 said:
I read the description of the rom and saw that it boots slow and left it 35 minute by the watch before giving up. That was the only thing that it didn't work,the fact that it didn't boot.
Click to expand...
Click to collapse
well i have no idea what you flashed with fastboot but you seem to have messed up good if the factory stock rom won't boot
cosminvr27 said:
Yes I did, the only problem is that it will not boot. It gets stuck at the first honor logo.
It only booted when I tried the first solution but in that case again it was showing 'unknown device' '1 gb of ram' etc.
Click to expand...
Click to collapse
When it sticks at logo boot in bootloader mode and fast boot flash the stock boot image then the phone WILL reboot as normal mate
Trust me it happened to me and that sorted it
Sent from my KIW-L21 using Tapatalk
chubby65 said:
When it sticks at logo boot in bootloader mode and fast boot flash the stock boot image then the phone WILL reboot as normal mate
Trust me it happened to me and that sorted it
Sent from my KIW-L21 using Tapatalk
Click to expand...
Click to collapse
It worked, thank u very much mate1
cosminvr27 said:
It worked, thank u very much mate1
Click to expand...
Click to collapse
No worries mate glad you're all sorted
Sent from my KIW-L21 using Tapatalk
This happened to me also. I flashed SuperSU on my GR5 and it went on bootloop. So I searched for TWRP Backup but I flashed KIW the first time, so I searched again and found the file. After boot, my about phone is displaying the wrong info. And also the pc detects it as MSM8916 for arm64 with only 2GB space. Please help
{
"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"
}
---------- Post added at 05:47 AM ---------- Previous post was at 05:25 AM ----------
I can't edit or post another link ><"
ht*tp://i.imgur.com/IXvNPEr.png
ht*tp://i.imgur.com/79HFKGq.png
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
{
"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"
}
dvegaman said:
Anyone have a pair of these glasses and working on root access? Anyone interested? There are a group of us that would be really interested in finding a solution.
Click to expand...
Click to collapse
I have a pair of the FPV Drone Edition. Have side loaded a few apps. Haven't rooted since Galaxy S3 ( back on iPhone now) am interested to get this going
Hi !
It seems the rooting of intel devices follow the scheme:
-get bootimg
-patch it
-allow oem bootloader (voiding warranty and endangering future updates)
-flash the patched bootimg and pray
Is this correct or did i oversimplify or generalize too much or am i plain wrong, anyone ?
Greetings,
Ender
P.S. Greetings dvegaman
Bump.
Well, BUMP, goddamn
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
jdiegmueller said:
Just came across 2 pairs of these (BT-300s).
If the lack of interest in rooting is due to lack of hardware, reach out to me privately here on XDA; would happily donate one to kickstart some development efforts.
-jd
Click to expand...
Click to collapse
Bumping this one up. Have a new pair and looking to root to wake them up some.
Sent from my Moto Z (2) using Tapatalk
This may seem easy to others but I figured out how to do a factory data reset using ADB... something that would've helped when my BT-300 went into a boot loop last weekend...
***DO AT YOUR OWN RISK! NOT RESPONSIBLE FOR BRICKING, ETC..... (but it worked fine for me).
1. Install "minimal_adb_fastboot_v1.4.2_setup.exe" (google it and grab at your own risk) on your Windows PC.
2. Go to the BT-300 and:
a. Under Security allow unknown sources
b. Under Developer Options allow USB debugging and unlock bootloader.
3. Connect same powered up BT-300 to PC via USB cable.
4. Start up that minimal ADB program. It will open in command prompt.
5. Check connection by typing "adb devices"
Should see "EMBT3C device" on PC
6. Now type, "adb reboot recovery" and wait for android with triangle/exclamation point to appear after device reboots. You will notice the physical buttons flash purple too.
7. Press and hold power button. Also press Vol Up, then release Vol Up and finally release Power button.
You should now see the recovery menu including "wipe data/factory reset", cache clear, and so on...
NOW... if I could get recovery.zip image to restore if I "kill" it to reload with ADB... THEN I'd try root. There must be a way. I just want GApps 5.1.1 on the thing for starters.
Still struggling with rooting... No dice so far. I've never rooted any Android... Once rooted can we then save the original factory ROM someplace safe, or do I need that first from another source? Newbie questions . I know just enough to be dangerous! LOL.
I got the factory image
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Erodros said:
Played around with the "SoftwareUpdate" apk and found the strings it uses to download the 1.4
Ugh just signed up but because I don't have enough posts I had to put a bunch of spaces in the links for them to
show up. Just remove the spaces and they should work? Either his or copy the SoftwareUpdate.apk and pull the strings from that.
ht tps:// download.ebz.epson.net /dsc /du /04 /SecureUpdateInfo ?PRN=BT-300&CTI=80&OSC=ARD&SCD=H756EMBT3C&SID=012345
You download a file called "SecureUpdateInfo" open it in a text editor and it will give you a link to the direct download for the zip. Its about 300megs. I have been playing with the boot options, but keep crashing it on boot and having to restore. I found 4 test pins that may be a serial port, but its 1.8 volt so I need to build something
PS - It might com back without a link but "BUSY" on it. I have been testing it a bunch so thats what happened right now. The fille will look like below
Code:
; secure update information
[BT-300;]
Version=R1.4.0
Size=371659424
Location= ht tps:// download.ebz.epson.net/ dsc/check/ 01/ GetFile. php ?PATH=xxxxxxx/OTA-R1.4.0.zip&KEY=lt1fs0DK
DownloadNumber=11474485
LALocation1=h ttp:// download.ebz.epso n.net/ dsc /hmd_license /EULA.zip
Click to expand...
Click to collapse
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Erodros said:
Is the link in the in the secureupdate? I don't know if the strings encode the serial number in some why or if epson is reading this thread
I can pm you a link for the file if you can't get it
Click to expand...
Click to collapse
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
chuck1026 said:
Yes, pm me the link. Thanks
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Erodros said:
Ok sending now.
I also managed to root my epson! I discovered the twrp.img here:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
If you get into bootloader mode and fastboot flash it into the recovery partition, you can adb root it and then install supersu from there. I just trashed my device though so be sure to do a full image backup first haha.
Click to expand...
Click to collapse
You trashed it? What did ya load after root to crash it?
chuck1026 said:
You trashed it? What did ya load after root to crash it?
Click to expand...
Click to collapse
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Erodros said:
Tried to load up opengapps, then every time I rebooted it would be "optimizing apps" I tried to side-load the OTA again and poof, it killed the system partition.
The ota apparently doesn't have the full image. Right now I am trying to hack together something from another cherry rom and side load it, but I need a DD of someones system Glad twrp still works or I wouldn't have shell root access to fix.
Click to expand...
Click to collapse
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
chuck1026 said:
You tell me how to share a pure factory image of mine (I'll gladly do an FDR for the cause)... and I'll share with ya!
Click to expand...
Click to collapse
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
PS - Ok, I figured out how to restore the original recovery loader and it recovered fine. It must be something in this hacked version of twip that isn't applying the ota correctly. Going to try to build a version of twip just for this
Erodros said:
Ok I am retarded. I didn't configure twp correctly so all the folders it had were wrong. So when I went to use the install tool it screwed up majorly.
Just glad I didn't overwrite the bootloader
Click to expand...
Click to collapse
You are not. I am the noob trying to figure out the whole root process and I don't even know how to backup the existing bootloader and ROM so I can restore it with ADB if I screw it all up in root..... I feel clueless and know just enough to be dangerous... yet for some reason, I'm not afraid, just need to learn.
chuck1026 said:
I am both impressed with your progress and baffled why I after I download SecureUpdateInfo I can't get to the zip file. Grrrrrrr.
Click to expand...
Click to collapse
Whew! I did it. First I took the instructions from here as a start:
https://forum.xda-developers.com/android/development/root-tutorial-intel-atom-cherry-trail-t3468330
In fact, if you can "almost" follow the instructions verbatim. The problem is that the data drive is encrypted and the default android password didn't work so I had to modify the boot.img to not encrypt the data partition then do a wipe. supersu installed fine then.
As for gapps, that was tricky. You have to manually install google webview apk as the built in one is garbage.
Still working on the vr settings. Camera has issues with scaling as I think good believes it to be a widescreen when its a 4.3.
Once I get it down, I will make a boot.img and recovery.img that should just work.
If anyone looking for root method, I can inform that magisk pre-patched boot.img works fine.
I just did a bootloader unlock tonight, patched the boot.img, and flashed through fastboot. Once booted I could install magisk from magisk manager.
{
"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 want to flash through TWRP instead, have a look at this post by @Bartoshevsky : https://forum.xda-developers.com/showpost.php?p=79358364&postcount=89
I will add pre patched boot.img's here
Can you post a guide or the a link for a magisk pre-patched boot.img ?
Woh, great!
Thanks for trying. For me this will be the best way, without any TWRP. Please, which version did you used: 17.1 (stable) or 17.3??
dare2k said:
Can you post a guide or the a link for a magisk pre-patched boot.img ?
Click to expand...
Click to collapse
I'll try to make a guide during the night, or tomorrow.
Here's a link to the pre-patched boot.img in this post. it's taken from XT1941-4 , buildnr OPKS28.63.18-3.
https://www.androidfilehost.com/?fid=11410963190603856664
Here's a good guide for bootloader unlock: https://forum.xda-developers.com/one-power/how-to/guide-motorola-one-power-unlock-relock-t3858797
So, short version here:
Unlock bootloader.
Install Magisk manager.
Go to fastboot and flash the patched boot.img
Reboot and open Magisk manager to install Magisk.
Profit!
Sylvia said:
Woh, great!
Thanks for trying. For me this will be the best way, without any TWRP. Please, which version did you used: 17.1 (stable) or 17.3??
Click to expand...
Click to collapse
I used 17.1, as seen in the screen shot
Don't use beta for everyday use unless you have to. It does a lot a verbose logging for debug, so it can even decrease performance of the device.
tys0n said:
I used 17.1, as seen in the screen shot
Don't use beta for everyday use unless you have to. It does a lot a verbose logging for debug, so it can even decrease performance of the device.
Click to expand...
Click to collapse
Sorry, I haven't noticed the screenshot.
And meanwhile I tried it myself. The result was a bootloop (17.3):crying:
Now I have seen your reply, downloaded the pre-patched boot.img and flashed this one. AND: All is fine now, I have a rooted device:good:!!!!!
Thank you so much, you saved my weekend
I presume for Pie we need another patched boot.img
dare2k said:
I presume for Pie we need another patched boot.img
Click to expand...
Click to collapse
Yes, that's right. I got the Pie update yesterday so hopefully I'll try to root it tonight.
tys0n said:
Yes, that's right. I got the Pie update yesterday so hopefully I'll try to root it tonight.
Click to expand...
Click to collapse
Wow nice! That would be awesome!
tys0n said:
Yes, that's right. I got the Pie update yesterday so hopefully I'll try to root it tonight.
Click to expand...
Click to collapse
How did you install the update? OTA doesn't work for me and when I try to unroot it says that there is no original file (of course not, I used your prepatched file)
dare2k said:
Wow nice! That would be awesome!
Click to expand...
Click to collapse
Unfortunatly that didn't work out well for me. I got in to some nasty boot problems and no matter what I did, it was always stuck at bootlogo. I gave it to a friend who's good at fixing these kind of problems but to no avail.
I really don't know what went wrong. Factory reset, re-flash firmware etc..nothing worked. As a last attempt we tried to boot slot _b instead but that was fatal.
It is now recognized as a Qualcomm HS-USB QDLoader 9008 so I can't even reach fastboot. lol Got no hope in finding a blank flash for it neither.
Sylvia said:
How did you install the update? OTA doesn't work for me and when I try to unroot it says that there is no original file (of course not, I used your prepatched file)
Click to expand...
Click to collapse
Sorry for late answer. I unrooted from magisk and flashed back stock boot.img taken from the firmware-package.
Anyway, I got a used one cheap so I still own the device. Won't try to root Pie again though. Not without TWRP.
Now I'm not sure whether I should upgrade or run it on rooted Oreo :/
tys0n said:
Unfortunatly that didn't work out well for me. I got in to some nasty boot problems and no matter what I did, it was always stuck at bootlogo. I gave it to a friend who's good at fixing these kind of problems but to no avail.
I really don't know what went wrong. Factory reset, re-flash firmware etc..nothing worked. As a last attempt we tried to boot slot _b instead but that was fatal.
It is now recognized as a Qualcomm HS-USB QDLoader 9008 so I can't even reach fastboot. lol Got no hope in finding a blank flash for it neither.
Sorry for late answer. I unrooted from magisk and flashed back stock boot.img taken from the firmware-package.
Anyway, I got a used one cheap so I still own the device. Won't try to root Pie again though. Not without TWRP.
Now I'm not sure whether I should upgrade or run it on rooted Oreo :/
Click to expand...
Click to collapse
Do you have the Dean codename? @tys0n
---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------
If so, Alberto posted on my thread with TWRP attempt
tys0n said:
Unfortunatly that didn't work out well for me. I got in to some nasty boot problems and no matter what I did, it was always stuck at bootlogo. I gave it to a friend who's good at fixing these kind of problems but to no avail.
I really don't know what went wrong. Factory reset, re-flash firmware etc..nothing worked. As a last attempt we tried to boot slot _b instead but that was fatal.
It is now recognized as a Qualcomm HS-USB QDLoader 9008 so I can't even reach fastboot. lol Got no hope in finding a blank flash for it neither.
Sorry for late answer. I unrooted from magisk and flashed back stock boot.img taken from the firmware-package.
Anyway, I got a used one cheap so I still own the device. Won't try to root Pie again though. Not without TWRP.
Now I'm not sure whether I should upgrade or run it on rooted Oreo :/
Click to expand...
Click to collapse
I have updated without unrooting! Found a script how to do here: https://forum.xda-developers.com/showpost.php?p=78302865&postcount=22 And without erasing data partion.
Than I rooted as you describe for 8.1...
Sylvia said:
I have updated without unrooting! Found a script how to do here: https://forum.xda-developers.com/showpost.php?p=78302865&postcount=22 And without erasing data partion.
Than I rooted as you describe for 8.1...
Click to expand...
Click to collapse
Wooh, that's awesome! I have no idea why it didn't work for me on P, but yeah..
I'll probably update and try again then Thanks for sharing.
borksek said:
Do you have the Dean codename? @tys0n
---------- Post added at 06:15 PM ---------- Previous post was at 06:14 PM ----------
If so, Alberto posted on my thread with TWRP attempt
Click to expand...
Click to collapse
Yes, it's deen, XT1941-4
Sylvia said:
I have updated without unrooting! Found a script how to do here: https://forum.xda-developers.com/showpost.php?p=78302865&postcount=22 And without erasing data partion.
Than I rooted as you describe for 8.1...
Click to expand...
Click to collapse
So, if I understood well, now you have Rooted Pie on the One? I am really interested in knowing how you got to do this, and I got lost in the Root-Update-reroot thing. Could you please explain what you did?
Thanks a lot
It works for me under Pie, too.
I patched the Stock boot.img with Magisk Manager and then flashed the created patched_boot.img with fastboot.
fastboot flash boot_a patched_boot.img
Finish...root at Android P
(XT1941-4 - OPENNEU)
1. Unlocked the bootloader: UNLOCK YOUR BOOTLOADER
2. Flashed the patched_boot.img via fastboot (even from OPENEU on RETEU ROM)
3. Completed the Magisk v17.1 installation from the Magisk Manager v6.0.1
4. Enjoying root on Pie 9.0 One.
To what partition do you flash the image?
Polyparadox said:
To what partition do you flash the image?
Click to expand...
Click to collapse
"fastboot flash boot patched_boot.img" works fine
Skickat från min Moto G5 via Tapatalk
tys0n said:
"fastboot flash boot patched_boot.img" works fine
Skickat från min Moto G5 via Tapatalk
Click to expand...
Click to collapse
Thanks, but I've got root. Although I'm not exactly sure how but I think it was this way:
Boot up TWRP
Format Data (not wipe)
Install Magisk (I used sideload)
Start your phine normaly and waot till its booted up
I installed Magisk Manager and saw that I was rooted.
Link to TWRP.
Hello friends all right? then, my phone just had a brick and I needed to return to stock rom, but the updates that were available I downloaded and installed, but not arrived android 11 with the realme ui 2.0, but was i used before, but as my smartphone just gave brick needed to downgrade now I can no longer update via OTA to android 11, does not appear to me, someone can help me?
RMX2155
Got the same issue too but for me I was trying to unlock the bootloader. Was on android 12 but after following the steps to unlocking the bootloader I am now stuck on android 10 and my bootloader is still locked
RMX2155
BBlackrn said:
Hello friends all right? then, my phone just had a brick and I needed to return to stock rom, but the updates that were available I downloaded and installed, but not arrived android 11 with the realme ui 2.0, but was i used before, but as my smartphone just gave brick needed to downgrade now I can no longer update via OTA to android 11, does not appear to me, someone can help me?
RMX2155
Click to expand...
Click to collapse
Incarcecon said:
Got the same issue too but for me I was trying to unlock the bootloader. Was on android 12 but after following the steps to unlocking the bootloader I am now stuck on android 10 and my bootloader is still locked
RMX2155
Click to expand...
Click to collapse
updates for RMX2155 model are not being available via settings, it seems to be some kind of sever issue, you can manually update by using sp flash tool, but only do this if you know what you are doing, this will delete your data.
also unlocked bootloaders are facing similar issues with updates, you should relock the bootloader if you want to update.
you can unlock/relock bootloader by using these kind of tool (MTK universal v5)
{
"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"
}
Incarcecon said:
Got the same issue too but for me I was trying to unlock the bootloader. Was on android 12 but after following the steps to unlocking the bootloader I am now stuck on android 10 and my bootloader is still locked
RMX2155
Click to expand...
Click to collapse
I have fixed this issue all you need is Android 11 ota update update from Android 10 settings then u will start receiving updates
Raghav. said:
I have fixed this issue all you need is Android 11 ota update update from Android 10 settings then u will start receiving updates
Click to expand...
Click to collapse
Wdym u dude?
Should I wait until the update just pops up or is there a way to do it manually
I tried to download the .zip file from realmefirmware.com and flash it thru recovery mode but it says : "Installation Failed"
tony 54325 said:
updates for RMX2155 model are not being available via settings, it seems to be some kind of sever issue, you can manually update by using sp flash tool, but only do this if you know what you are doing, this will delete your data.
also unlocked bootloaders are facing similar issues with updates, you should relock the bootloader if you want to update.
you can unlock/relock bootloader by using these kind of tool (MTK universal v5) View attachment 5794063
Click to expand...
Click to collapse
bro can u plz post a small tutorial on how to do it plz i really need to get back to rui3.0 thx in advance
DaCrab said:
bro can u plz post a small tutorial on how to do it plz i really need to get back to rui3.0 thx in advance
Click to expand...
Click to collapse
Follow this tutorial:
But instead of stock a53(RUI1) frimware you need for download F09(RUI3) frimware for rmx2151, can't paste link here because it will be removed,
After extraction of Ofp file you'll get multiple super.img and one supermap.xml type file..
You only need one super.img, for that you'll need simg2img.exe,
After downloading simg2img.exe put it in the same folder where you extracted the ofp and open cmd in the same folder,
And type following command "simg2img.exe super.xxx.img super.yyy.img super.zzz.img super.img"
where x,y,z will be replaced by names present in supermap file ..
Then you'll have a new file in ofp folder named super.img,
Follow rest of the tutorial afterwards...
You also might need to unlock bootloader.
so im looking at realmefirware(.com) but i cant find the F09 firmware only the C.19 version idk if thats it
I also checked the link in the tutorials description and the codename is RMX2163 and i also dk if its the right files
the last thing i wanna do now is to brick my device
DaCrab said:
so im looking at realmefirware(.com) but i cant find the F09 firmware only the C.19 version idk if thats it
I also checked the link in the tutorials description and the codename is RMX2163 and i also dk if its the right files
the last thing i wanna do now is to brick my device
Click to expand...
Click to collapse
its available on "gsmmafia"
tony 54325 said:
its available on "gsmmafia"
Click to expand...
Click to collapse
Btw u thing rooting is worth it (not only for the custom roms but for the modules and the endless possibilities that root unlocks)
DaCrab said:
Btw u thing rooting is worth it (not only for the custom roms but for the modules and the endless possibilities that root unlocks)
Click to expand...
Click to collapse
Depends on the situations,
If you have only one phone and you are a corporate guy, then its probably not worth it
Also now a days most of the little customisations(including custom roms) can be achieved without root.
However if you plan to root your secondary phone and do all kind of kinky stuff with it then its absolutely fun,
Root always comes with risk.
magnumoZeus said:
Follow this tutorial:
But instead of stock a53(RUI1) frimware you need for download F09(RUI3) frimware for rmx2151, can't paste link here because it will be removed,
After extraction of Ofp file you'll get multiple super.img and one supermap.xml type file..
You only need one super.img, for that you'll need simg2img.exe,
After downloading simg2img.exe put it in the same folder where you extracted the ofp and open cmd in the same folder,
And type following command "simg2img.exe super.xxx.img super.yyy.img super.zzz.img super.img"
where x,y,z will be replaced by names present in supermap file ..
Then you'll have a new file in ofp folder named super.img,
Follow rest of the tutorial afterwards...
You also might need to unlock bootloader.
Click to expand...
Click to collapse
btw dude can u share any guide on this one cause it seems its the only way ( at least for me ) to unlock my bootloader cause i cant do it thru the deep test (or in-depth test ) idk why.
Unlocking the bootloader might be more useful for me rather than flashing back to rui3.0
thx for all the help fam very much appreciated
DaCrab said:
btw dude can u share any guide on this one cause it seems its the only way ( at least for me ) to unlock my bootloader cause i cant do it thru the deep test (or in-depth test ) idk why.
Unlocking the bootloader might be more useful for me rather than flashing back to rui3.0
thx for all the help fam very much appreciated
Click to expand...
Click to collapse
there are tons and dozens of tutorials available online on how to unlock the bootloader,
you can use tools like this
, and there are many more tools available,
quick tutorial steps :
1 click on install drivers
2 select device
3 power off phone
4 click unlock bootloader
5 connect phone using company usb cable, while holding volume up and down key together (in power off state)
done!!!!
magnumoZeus said:
there are tons and dozens of tutorials available online on how to unlock the bootloader,
you can use tools like thisView attachment 5808179 , and there are many more tools available,
quick tutorial steps :
1 click on install drivers
2 select device
3 power off phone
4 click unlock bootloader
5 connect phone using company usb cable, while holding volume up and down key together (in power off state)
done!!!!
Click to expand...
Click to collapse
aye bro sorry for bothering you all the time but i really dont know anything about this whole thing and as it seems u r the only one that can help me
but i unlocked my bootloader and got into a Orange State which cause my system to reboot to recovery can u help me with that fam
thanks for ur time.
DaCrab said:
aye bro sorry for bothering you all the time but i really dont know anything about this whole thing and as it seems u r the only one that can help me
but i unlocked my bootloader and got into a Orange State which cause my system to reboot to recovery can u help me with that fam
thanks for ur time.
Click to expand...
Click to collapse
No problem buddy, just keep searching for solutions.
Orange state is just a msg to inform you that your boot loader has been unlocked,
while in recovery format and wipe data, then reboot.
And next time try to add images also.
And if you plan on using sp flash tool it doesn't matter if your phone is booting or not.
magnumoZeus said:
No problem buddy, just keep searching for solutions.
Orange state is just a msg to inform you that your boot loader has been unlocked,
while in recovery format and wipe data, then reboot.
And next time try to add images also.
And if you plan on using sp flash tool it doesn't matter if your phone is booting or not.
Click to expand...
Click to collapse
So to get this right
Once I unlock the bootloader I will get into the the Orange state which I will able to bypass by formating (wipe data) on my phone and I should be able to boot again right ? On the original rom
And from there I will be able to install the TWRP custom recovery in which I can install my custom rom ?
Right?
DaCrab said:
So to get this right
Once I unlock the bootloader I will get into the the Orange state which I will able to bypass by formating (wipe data) on my phone and I should be able to boot again right ? On the original rom
And from there I will be able to install the TWRP custom recovery in which I can install my custom rom ?
Right?
Click to expand...
Click to collapse
Didn't you said you already unlocked your bootloader
yeah i did but then relocked it to use my phone , i cant use it with the orange state
magnumoZeus said:
No problem buddy, just keep searching for solutions.
Orange state is just a msg to inform you that your boot loader has been unlocked,
while in recovery format and wipe data, then reboot.
And next time try to add images also.
And if you plan on using sp flash tool it doesn't matter if your phone is booting or not.
Click to expand...
Click to collapse
If I format my device while on Orange state will I able to bypass it and install TWRP (or any other custom recovery)
Or I need to do something else ?
Look brother i have managed to bypass that error but now i cant boot to fastboot thru ADB whenever i try it prints some zeros and at the bottom fastboot verification failed can u help me with that?
Also idk how to delete the quotes above