Hi guys im new to the nexus 7, i have previously owned a samsung galaxy s wifi 4.0(piece of crap), i had unlocked and rooted my nexus using the nexus root toolkit v1.6.3. Then i flashed francos latest release kernel through the francos kernel app, Next i downloaded the beats+xlouder mod, i attempted to flash it through cwm by installing zip, it seemed to work, booted then said, something about configuring apps and it got stuck on that. I tried rebooting many times but it didnt work. So then i tried to flash a nandroid backup i had made through the toolkit, this failed. Now i have been trying to flash the nakasi factory image through the toolkit, here is the message i get;
{
"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"
}
Anyone have any ideas as to whats going on? and how i might get the nexus working again?
Don't use toolkits.
Apparently, your bootloader won't flash correctly. What version is your bootloader now? If you want to flash android 4.2.2, then it should be 4.18.
Check your USB-cable. If possible, use the one that came with the nexus 7. Check your bootloader img-file. Is the md5-sum correct? If uncertain, then redownload the firmware here: https://developers.google.com/android/nexus/images#nakasi
Extract the contents of the firmware file in your folder with adb and fastboot.
Put your nexus 7 in fastboot/bootloader mode (you can do this by pushing all three buttons on the sides simultaniously).
Type (this will erase everything from your device):
: fastboot erase boot
: fastboot erase cache
: fastboot erase recovery
: fastboot erase system
: fastboot erase userdata
If you need to update your bootloader, then type:
: fastboot flash bootloader bootloader-grouper-4.18.img
If you get an error like signature failed, then recheck your USB cable. This should work. If not, then download the android 4.1.2 firmware and skip flashing the bootloader. You can do an OTA update later.
: fastboot reboot-bootloader
Then type:
: fastboot -w update image-nakasi-jdq39.zip
I had a few troubles on my first attempts too... My suggestion is to get Nexus7 Toolbox from the Sticky in the Development section and flash the image you have, that always worked without a hitch for me!
Good luck!
Is it really important to use the USB cable that was delivered with the device? Did not know there's a difference!
Sent from my Xperia Tipo using xda premium
random hero said:
Is it really important to use the USB cable that was delivered with the device? Did not know there's a difference!
Sent from my Xperia Tipo using xda premium
Click to expand...
Click to collapse
Probably not, but I have seen forum posts where people reported different experience with different cables used to flash firmware. I only experience it when charging. My nexus charges faster with the original cable and charger. Also the original cable's small end is slightly longer than the small end on the cable I got with my samsung smartphone. If it makes any difference when flashing? I am not sure, but to rule out bad USB-cables as a reason for firmware not flashing I always use the original cable.
My bootloader versin is 4.18, how exactly do i check md5 sums,?
i have no experience with fast boot and adb, are they pc programs? If so cqn you give me a link to them?
Sorry im sure you guys get sick of idiots like me asking questions all day but i really appreciate the help
If your bootloader version is 4.18, then there is no need to reflash it and you can skip this step. Don't worry about feeling idiotic for asking questions. Up until I first rooted my nexus, I had no idea how everything worked either. I learned everything by myself, but it's not that easy for everyone.
You can find adb and fastboot in the folder platform tools in the official google android SDK. Instead of downloading the entire SDK, you can also just download the latest platform tools online from many file share websites: https://mega.co.nz/#!1c1XjIIC!dTyG200R4V3BPIfrac4xayEttP02f9tYlPkqAlqvTko .
Extract that folder. Go to that folder. Hold shift and click with your right mouse button and select open terminal prompt.
Now you can use fastboot to flash images, recoveries, bootloaders, erase your devices, restore, etc.....
yeah ok, ill try it and fingers crossed that it works
i tried to flash it but it says
error: failed to load 'image-nakasi-jdq39.zip
the file i have is a .tar, would that be the problem?
Yes! We found the problem.
You need to unzip the tar file as well. 7-zip can do this for example.
thanks guys i got it to work, any suggestions for a fast and stable rom?
:laugh:
TheFro74 said:
thanks guys i got it to work, any suggestions for a fast and stable rom?
:laugh:
Click to expand...
Click to collapse
http://www.modaco.com/forum/657-google-asus-nexus-7-nexus7modacocom ... but I would say that wouldn't I, given it's my own ROM of choice.
Leaving aside my own personal preferences, check out these two threads for ideas and recommendations...
http://forum.xda-developers.com/showthread.php?t=2151963
http://forum.xda-developers.com/showthread.php?t=1807811
The question you have to ask yourself is... do you want full-on functionality, with shed-loads of bells and whistles... or a lean, mean, and minimalistic ROM... or, perhaps something inbetween.
The choice, as they say, is yours....
Rgrds,
Ged.
One of the fun things about the nexus 7 is to experience different roms yourself. See what they differ, what they have in common, what you like about them, etc. I liked paranoid android a lot. I found it very creative, but it didn't ran fluent for me. I even tried ubuntu, but that's just not ready for daily use yet. Now I settled for CM 10.1 M3. It's very stable, smooth and provides a better experience than stock, which I was looking for. But it might be too basic for you. Try it out! And make NANDROID BACKUPS before you do!
Thanks guys , my current setup is a cm10.1 snapshot with Franco's kernel.
Sent from my Nexus 7 using xda app-developers app
Related
Do it at your own risk and read it carefully!
I combine the guide for ICS and JB flashing.
- Download the latest driver for Windows HERE and for Mac HERE.
- Download RSD Lite HERE.
- Download stock ICS HERE
- Download stock JB HERE
- You need to open the zip of the rom and find xxx.xml. Open it and notice line like . You should remove both lines to avoid error at flashing. Or you can download my modified xml for ICS HERE. For JB HERE. Replace your original xml.
- Install drivers and RSD Lite to your PC.
- Make sure your battery at least 80% before we proceed.
- Turn off your phone and press both volume keys and power on. You'll enter bootmenu options. Choose AP Fastboot by scrolling with volume down and volume up to select.
- Connect your phone to PC and your PC will detect and install the drivers automatically.
- Open RSD Lite and click ... beside filename. Browse to your ROM and double click it. A menu will popup and choose "uncompress and start flashing".
- It will start flashing once it finishes uncompressing.
- Sit down and relax.
If you want to replace stock recovery with CWM,you can do it by replacing THIS over the original one inside the zip. Thanks to skeevy420.
Note : You can't downgrade if you are on JB to ICS via RSD Lite. With an unlocked bootloader,you can do that with fastboot.
Screenshot added to second post. Thanks a lot to devilsking.
Ha ha. Finally U did it . and now I found an useful guide of how to flashing stock firmware :">. But it's better to add screenshots then make ur guide more clear so I will help u to finish it. Anw, Thank you bro
1. After download required files, open stock rom (*.zip) and you need to find the xml file with name of firmware:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Open that xml file with notepad (I recommend Notepad ++) and delete 2 get var lines then save it:
3. Open the fastboot mode (Turn off your phone and press both volume keys and power on then select by volume +, scroll by vomlume - or )
4. Open RSDlite, select firmware with edited xml and let it decompress then flash.
Nice,bro.. I'll edit my post and insert your pictures when I'm on PC. It will be better with pictures. Thanks,bro..
Sent from my XT897 using Tapatalk 2
huatz84 said:
Nice,bro.. I'll edit my post and insert your pictures when I'm on PC. It will be better with pictures. Thanks,bro..
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Just write a note about screenshots in post #2 is ok. No need to re-insert pictures becoz it makes double contents
devilsking said:
Just write a note about screenshots in post #2 is ok. No need to re-insert pictures becoz it makes double contents
Click to expand...
Click to collapse
Added! Thanks,bro..
Sent from my XT897 using Tapatalk 2
To expedite things a bit, you could also add to the OP to change the md5sum of the fastboot's recovery.img and replace stock recovery with Epinter's CWM. Don't have Windows to test so I'm not sure if it'll work, but it should. That way they don't have to "fastboot flash recovery recovery.img" afterwards.
md5sum=0437ea5bba4433c0e8387493afb821cd
skeevy420 said:
To expedite things a bit, you could also add to the OP to change the md5sum of the fastboot's recovery.img and replace stock recovery with Epinter's CWM. Don't have Windows to test so I'm not sure if it'll work, but it should. That way they don't have to "fastboot flash recovery recovery.img" afterwards.
md5sum=0437ea5bba4433c0e8387493afb821cd
Click to expand...
Click to collapse
Thanks,bro.. so after replacing stock recovery.img,we'll end with epinter's cwm instead of stock? This is useful for those who don't want to do fastboot cmd things. I'll add it soon. I'm on my Photon Q right now.
Sent from my XT897 using Tapatalk 2
huatz84 said:
Thanks,bro.. so after replacing stock recovery.img,we'll end with epinter's cwm instead of stock? This is useful for those who don't want to do fastboot cmd things. I'll add it soon. I'm on my Photon Q right now.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Exactly.
That's what I was thinking.
HELLP!!!! pleace
skeevydude said:
Exactly.
That's what I was thinking.
Click to expand...
Click to collapse
Hello friend, I have a At & t AHD MB886 native JB. when I did a factory reset is hung up and when it starts motorola logo appears and then the screen goes black and does nothing enlightened, did hard reset, recovery, all you can do and the machine will not start. What I can do? the tutorial "How To Flash Stock ROM With RSD Lite" work??
fedefenix said:
Hello friend, I have a At & t AHD MB886 native JB. when I did a factory reset is hung up and when it starts motorola logo appears and then the screen goes black and does nothing enlightened, did hard reset, recovery, all you can do and the machine will not start. What I can do? the tutorial "How To Flash Stock ROM With RSD Lite" work??
Click to expand...
Click to collapse
It should.
ok
fedefenix said:
Hello friend, I have a At & t AHD MB886 native JB. when I did a factory reset is hung up and when it starts motorola logo appears and then the screen goes black and does nothing enlightened, did hard reset, recovery, all you can do and the machine will not start. What I can do? the tutorial "How To Flash Stock ROM With RSD Lite" work??
Click to expand...
Click to collapse
achievement and time to install and works well, the only problem is that I connect to the wifi network, I will keep trying
May be a baseband / modem problem follow my tutorial
here.
Couldn't flash stock via fastboot after CM10, this was very helpful. Thank you.
Sticky bit factory_fastboot and flash failure at 17/21 in rsd lite. Any suggestions?
Sent from my MB886 using xda premium
helldogg75 said:
Sticky bit factory_fastboot and flash failure at 17/21 in rsd lite. Any suggestions?
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
Make sure your harddisk has at least 3gb free space. Try reflashing it.
This is nice, thank you.
Works Great For Me
now i have a Motorola Atrix HD with Bootloader unlocked and Recovery but when i try to put a new Rom in the Phone Dont Put the new Rom overwrite the Rom in the AT&T Rom (try with Batakang Rom) if i try with Cyanogen or another dont give Me that Problem ?
Um what?
Sent from my JokerMATRIX HD MAXX
Did you mount /system before flashing Batakang? For roms intended for flashing in SafeStrap, like Batakang, to flash in CWM you must mount /system first.
You know what they say... Once you go Android, you don't go back. Flashaholic for sure.
Hi
Follow the instructions mentioned on this website and your good go ... I bricked mine last night trying to figure out how to switch network bands and used this one to get my device back and going
Hope it helps
"theunlockr.com/2013/03/05/how-to-unroot-the-motorola-atrix-hd/
Sent from my MB886 using xda app-developers app
Hi,
I downloaded CWM unofficial 6.0.32 from this forum, but I'm new and I have no idea what to do with it. I did successfully root my phone that's all I've done to it.
Thanks!
You use fastboot commands. There's a tutorial skeevy just made in general.
Sent from my PACMAN MATRIX HD MAXX
I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.
Do you have the lastest motorola usb driver installed?
hungrymr2 said:
Do you have the lastest motorola usb driver installed?
Click to expand...
Click to collapse
Yes, Sir
Rick1488 said:
I'm sorry, but I'm getting stuck
1: I installed the sdk replaced the files with the updated ones provided.
2:checked adb devices from command promt and It sees my device.
3: ran adb and it successfully starts
4: I then rebooted phone into fastboot Power+Volume down and adb reports device not found.
5: pull hair out.
I'd appreciate a sort of idiots guide because I'm getting no where fast and I've read and read, but they don't explain much that's the problem.
Click to expand...
Click to collapse
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....
No idea, but here's what I did to install cwm. download safestrap apk, boot to safestrap recovery, hit fix permission, go back to cmd prompt, fastboot flash it,
edit: try enabling "usb developer/debugging mode" before booting it into fastboot?
skeevydude said:
1. :good:
2. :good:
3 :good:
4 You're in fastboot mode....adb won't recognize your phone....that's normal...
5
use the command "fastboot flash recovery cwm.img" from inside the folder with cwm.img. Or move the fastboot executable and the recovery image to C:\ and do it from there...Win can crap out when/if there are too many characters in the path...
Also, right click the fastboot executable and set it to run as admin. Might have to disable UAC as well....don't ask me how, I don't know...google it.
//I'm cereal, ya had to rename the SBF because in the home directory the path + sbf name would be too many characters for Win to work with and the flash would fail....
Click to expand...
Click to collapse
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
{
"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"
}
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.
Rick1488 said:
Ok your directions were very helpful and I thought good things were coming my way, but when entering the flash command I get preflash validation failed. <failed> remote failure.
Update: now the phone boots to fastboot with flash failure on the bottom. What the hell did I do wrong?
Update2: ok got her back to life back to the original problem.
Click to expand...
Click to collapse
You might have a picky motherboard. Some front-side ubs ports won't work for some odd reason for some users. Use a usb port on the back of your pc.
Out of curiousity, did you try flashing a fastboot with rsd before you started doing this? And if yes, did it finish completely?
Also attached is a zip to flash CWM from SSR (maybe...SSR might block the command) and a fastboot modified to only flash CWM. Both are untested but worth a shot.
EDIT: Any one of you windows users care to chime in? Ya'll know I don't run it. I'm kinda runnin outta ideas here....gettin down to the just use linux reply...
unlocked bootloader
I saw that you rooted but did you unlock the boot loader?
frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
You're right...can't believe I missed that...never once is that mentioned...,
frog1982 said:
I saw that you rooted but did you unlock the boot loader?
Click to expand...
Click to collapse
Um, I kinda forgot that part.. my fault. I just unlocked the bootloader and I'm gonna give it another try.
UPDATE: Success!
I'm sorry guys thanks for all your help.
:victory::victory:
Hi im trying to find if there has been proper recovery made for the x704a devices and if there is actually custom roms that support the x704a . I've searched and searched and cant find much solid info. I see tons of the 704f, l, etc. but cant find anything specific or will work with the x704a for sure. I have the tablet with the stock android 71.1. rom and its a buggy mess always lagging and have to restart multiple times a day just to be able to try to use it. And its done this from day one and even after reflashing the stock rom from scratch. Trying to find options to make this thing better vs throwing it in the trash and wasting the money i paid for it. All help would be appreciated . Thanks in advance
Hi I am using a recovery that works with the x704a its hard to find I will have a look for a link or I can send you the file.
Regards Ashley
Download the onekey unlock and the twrp.
The default language is Chinese.
https://drive.google.com/open?id=1H5k46hztwj_1FeBxzfFIXqo5hy0OpJvr
So what custom roms have you guys found for these?
Sent from my HD1925 using Tapatalk
This tablet blows...x704a
I watched tons of reviews on the Lenovo tab 10. All positive reviews. So, when I found a version with 1 less gig of ram but cellular support I jumped on it as a $200 gift for my wife. Lenovo, the Amazon seller used the same exact name for the x704f and x704a.. they are not the same , this tablet blows. I ended up getting her another tablet and we are stuck with this pos. I would like to get a rooted cfw like lineage and no luck so far.
I have the same problem! My tablet is a lenovo tab x704A and only information about x704F appears, I don't know if it is the same, then try with that info, unlock the bootloader, download the twrp recovery for x704F when flashing it tells me that the procedure was a success, but the device It does not restart in twrp recovery, I did everything using the commands, I did it manually from the tab and nothing is only the original recovery (oem) as if I had not installed it, it must be because that recovery is not compatible. If you can help me!
Tegra4Me said:
This tablet blows...x704a
I watched tons of reviews on the Lenovo tab 10. All positive reviews. So, when I found a version with 1 less gig of ram but cellular support I jumped on it as a $200 gift for my wife. Lenovo, the Amazon seller used the same exact name for the x704f and x704a.. they are not the same , this tablet blows. I ended up getting her another tablet and we are stuck with this pos. I would like to get a rooted cfw like lineage and no luck so far.
Click to expand...
Click to collapse
Are you talking about Lenovo Tab4 10 x704A ? Is that the one with the ATT logo on the back, cuz I have that (one with 2gb of ram) and its rooted with magisk and has lineage OS and works great. You do need a special twrp file though.
{
"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"
}
manny71 said:
I have the same problem! My tablet is a lenovo tab x704A and only information about x704F appears, I don't know if it is the same, then try with that info, unlock the bootloader, download the twrp recovery for x704F when flashing it tells me that the procedure was a success, but the device It does not restart in twrp recovery, I did everything using the commands, I did it manually from the tab and nothing is only the original recovery (oem) as if I had not installed it, it must be because that recovery is not compatible. If you can help me!
Click to expand...
Click to collapse
I have Lenovo tab x704A its one with the ATT logo on the back right? It uses a special twrp file that only works with x704A recovery-TWRP-3.3.0-0521-LENOVO_TBX704A-CN-wzsx150.img . No other x704 variants twrps work on x704A and I have tried. Download that try to flash that to your recovery. I used this ROM https://forum.xda-developers.com/t/...neageos-16-0-for-lenovo-tab4-10-plus.3923394/
I haven't gotten to try the newer OS10 Lineage 17.
Folty57fg said:
I have Lenovo tab x704A its one with the ATT logo on the back right? It uses a special twrp file that only works with x704A recovery-TWRP-3.3.0-0521-LENOVO_TBX704A-CN-wzsx150.img . No other x704 variants twrps work on x704A and I have tried. Download that try to flash that to your recovery. I used this ROM https://forum.xda-developers.com/t/...neageos-16-0-for-lenovo-tab4-10-plus.3923394/
I haven't gotten to try the newer OS10 Lineage 17.
Click to expand...
Click to collapse
So this rom works with the x704a?
Folty57fg said:
Are you talking about Lenovo Tab4 10 x704A ? Is that the one with the ATT logo on the back, cuz I have that (one with 2gb of ram) and its rooted with magisk and has lineage OS and works great. You do need a special twrp file though.
View attachment 5187855
Click to expand...
Click to collapse
Could you help me with step by steps to install the twrp which you provided. I have the same XB704A tablet and I’m not successful in installing this twrp. I’m stuck. Kindly reply here or mail me at [email protected]
Bhaskarrv said:
Could you help me with step by steps to install the twrp which you provided. I have the same XB704A tablet and I’m not successful in installing this twrp. I’m stuck. Kindly reply here or mail me at [email protected]
Click to expand...
Click to collapse
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Don't setup, cause you will need to format your tablet later again. Shutdown tablet. Hold volume up and power button to start to bootloader
Then run
Code:
fastboot flash recovery twrp-3.2.3-0-<your-filename>.img
to flash TWRP
Select with volume buttons "Recovery Mode" and press power button
Select to write to system, otherwise you can't flash ROM
Backup at least system and boot partitions to your sdcard cause you will wipe data in next step. Choose "System Image" for the system partition backup.
Flash the recovery that I mentioned. Recovery-TWRP-3.3.0-0521-LENOVO_TBX704A-CN
The instructions I used were from this thread.
[ROM][UNOFFICIAL][9.0][TB-X704F/L] LineageOS 16.0 for Lenovo Tab4 10 Plus
/* * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * Please do some research if you have any concerns about features included in the...
forum.xda-developers.com
Use the twrp that I link, its only compatible with our tablet model. I rename it to like twrp.img then use "fastboot flash recovery twrp.img" instead of typing the whole name of the img file.
marcmann982 said:
So this rom works with the x704a?
Click to expand...
Click to collapse
sorry for late response, yes it works with x704a that what I screenshot it, you need a specific TWRP to install ROM
I tried to uninstall magisk via twrp flashing boot.img but only appeared the fastboot screen, so tried to restore stock rom but still on fastboot
Tried MiFlash, XiaoMI tool v2, MiFlash Pro with so many fastboot roms, flashed custom roms (included the aosp derivates and the latest miui eu) and still no luck, at least twrp and custom recoveries works fine
Please help, I already spent to many days trying to fix it
Edit: Tried to flash vbmeta again and now it works
uninstalling magisk is pretty hard nowadays, even when uninstalling via the app (which also flashes the uninstaller)
something is very wrong since you redirect to fastboot
did you format data?
try flashing the vbmeta at the bottom of the post
GUIDE From Zero to Hero - Basic Usage
Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. YOUR WARRANTY IS VOID IF YOU CONTINUE A noob friendly guide on how to get the most out of your phone. The Xiaomi Redmi 8 has been touted as one of the most sold...
forum.xda-developers.com
what were the results when you flashed stock using tools? have you tried fastboot instead of using the gui tools (often verry buggy)
fonzacus said:
uninstalling magisk is pretty hard nowadays, even when uninstalling via the app (which also flashes the uninstaller)
something is very wrong since you redirect to fastboot
did you format data?
try flashing the vbmeta at the bottom of the post
GUIDE From Zero to Hero - Basic Usage
Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. YOUR WARRANTY IS VOID IF YOU CONTINUE A noob friendly guide on how to get the most out of your phone. The Xiaomi Redmi 8 has been touted as one of the most sold...
forum.xda-developers.com
what were the results when you flashed stock using tools? have you tried fastboot instead of using the gui tools (often verry buggy)
Click to expand...
Click to collapse
Basically i tried everything in the guide and other xiaomi guides (Except flashing via EDL), in the gui tools always show as "Success" and via fastboot all seems to be flashed correctly but still got the fastboot screen
Edit: Trying one more time with another vbmeta and instaled dotOS, Now it works
just a side note, miui >12.5.x were built to be more picky with everything in general. you mightve been blocked by miuis avb (custom vbmetas workaround this) when you were sent to fastb
hence why twrp 3.6.x includes an advanced installer option (workaround this and other brands)
as for trying to fully uninstall magisk, lots of others (including me) failed lots in the past on 23 and canary (and other forks), reinstalling again seems to fix it
thankfully you got it up and running, tho id recd something other than dot, i and others found it battery heavy for some strange reason ;P
good night in my case what happened to me is that I was cleaning the files see formatting the folders through orange fox recovery, after doing everything quietly I went to install the official rom of miui 12.5, because previously I had a custom rom of android 12 and I saw many problems with said rom anyway. I do a deep cleaning and proceed to install the official rom It gave me a very bad feeling that in the process it will restart in recovery at the end of everything, so I reinstalled the rom and instead of falling into recovery it falls into fastboot and restarts and It does not let you enter the recovery but goes directly to fastboot. The pc detects it as android and the tools only throw that code that it gives in the attached image. please a hand for this poor devil I don't want to lose such a good phone.
{
"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"
}
xXchizaXx said:
good night in my case what happened to me is that I was cleaning the files see formatting the folders through orange fox recovery, after doing everything quietly I went to install the official rom of miui 12.5, because previously I had a custom rom of android 12 and I saw many problems with said rom anyway. I do a deep cleaning and proceed to install the official rom It gave me a very bad feeling that in the process it will restart in recovery at the end of everything, so I reinstalled the rom and instead of falling into recovery it falls into fastboot and restarts and It does not let you enter the recovery but goes directly to fastboot. The pc detects it as android and the tools only throw that code that it gives in the attached image. please a hand for this poor devil I don't want to lose such a good phone.View attachment 5650943
Click to expand...
Click to collapse
you should make a new thread for this
so many questions
its a very delicate situation youre in. which orangefox? which miui rom? is your os really winxp? what does device manager see your phone as?
fonzacus said:
you should make a new thread for this
so many questions
its a very delicate situation youre in. which orangefox? which miui rom? is your os really winxp? what does device manager see your phone as?
Click to expand...
Click to collapse
Fortunately, you can install the Miui through the flash ROM, but unfortunately the Miui 11 version blocked me from starting up again, so I can't put any more ROMs in it.
So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
{
"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"
}
biglo said:
So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
View attachment 5694575
Click to expand...
Click to collapse
Are you rooted? Can you get in recovery? What model number?
twinnfamous said:
Are you rooted? Can you get in recovery? What model number?
Click to expand...
Click to collapse
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.
biglo said:
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.
Click to expand...
Click to collapse
Have you tried flashing stock boot.img or factory resetting?
twinnfamous said:
Have you tried flashing stock boot.img or factory resetting?
Click to expand...
Click to collapse
Yes, I tried both options without success.
biglo said:
Yes, I tried both options without success.
Click to expand...
Click to collapse
That's not good usually one or the other fixes it. Only thing I can think of is flashing all images in fastboot. But try vendor_boot first
When this happened to me on my OP6 when I had it and when I couldn't recover it with MSM tools or boot.img, I decided it is motherboard failure.
But I would try fastboot ROM if I were you. If it doesn't help, I will send it to the service center.
You may have booted a patched yet not made it permanent so when you rebooted you lost it.
If that rings a bell then just boot a patched boot image. Not flash.. once you're booted and in the system just open magisk and click direct install..
Reboot and it should be permanent.
Beyond that you can go to recovery or fastboot to get back in business although you'll lose your data
My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b
unsafe8989 said:
My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b
Click to expand...
Click to collapse
I tried switching slots the other day, it gave me the same results.
hello did you found any solutions?
biglo said:
I tried switching slots the other day, it gave me the same results.
Click to expand...
Click to collapse
That means you have no boot img on it
try to flash a boot img to slot a and slot b
Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.
dladz said:
Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.
Click to expand...
Click to collapse
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.
*-MaCK-* said:
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.
Click to expand...
Click to collapse
Doesn't help that the forums went through a crap update that broke the sections.
That being said, you're looking for a guide so that's your key word.
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
There's a good few of them, the screen shot is taken from the main OnePlus 10 pro forum section, I can see two. Mine and the 2215 one.
Also when you say 'installed' I hope you meant boot and not flash, booting is risk free.. Read my thread and it'll make sense.
I wish people would read more...cause it all here...just need to take the time and read alot of post...to find what they are looking for...lol