Related
I have just received my Iocean X7 Elite and was about to install a new rom. I had successfully rooted the device and then was trying to flash
the recovery with SP Flash Tool.
After the recovery flashed my phone refuses to turn on I believe its somehow bricked but have no idea how this could have happened. I did
format flash i only downloaded the recovery to the device.
In Device Manager when i plug the phone it it either shows up as 'DA USB VCOM Port' or 'MTK USB Port'.
When I try to use SP Tool to flash the stock Rom back onto the device I get an error saying 'BROM ERROR : S_FT_ENABLE_DRAM_FAIL(4032)'
I have no idea what to do next can someone help me.
I have tried what this thread suggests:
bump
same as u..but differ phone model.(N9589)
had a few upgrd...til the recent brick it.
Tried a few version of flash tool and still the same
Joshafc said:
I have just received my Iocean X7 Elite and was about to install a new rom. I had successfully rooted the device and then was trying to flash
the recovery with SP Flash Tool.
After the recovery flashed my phone refuses to turn on I believe its somehow bricked but have no idea how this could have happened. I did
format flash i only downloaded the recovery to the device.
In Device Manager when i plug the phone it it either shows up as 'DA USB VCOM Port' or 'MTK USB Port'.
When I try to use SP Tool to flash the stock Rom back onto the device I get an error saying 'BROM ERROR : S_FT_ENABLE_DRAM_FAIL(4032)'
I have no idea what to do next can someone help me.
I have tried what this thread suggests:
Click to expand...
Click to collapse
Same problem here - tried to install stock firmware and got this error...
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
tukulll said:
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
Click to expand...
Click to collapse
Thank you for your reply, but this doesn't help... ;(
Anyone?
I think I figured out that the error above means you are trying to flash an incorrect ROM. Make sure you are using the right one and also make sure you're using the latest version of sp flash tool.
Once I downloaded a later version of the flash tool it began installing the ROM but then a different error appeared.
So I formatted the nand with the sp flash tool.
Then I flashed the stock ROM again and it worked
Formatting it seemed to make the errors go away even though its advised not to do so.
Sent from my iOCEAN X7 using xda app-developers app
vessk0 said:
Anyone?
Click to expand...
Click to collapse
I fixed this error by completely removing and reinstalling other drivers for mtk vcom loader
anyone heard Iocean will recall all of the x7 elite's? i've had a mail today they should do it, but i don't know if it's true or not.
Schumi_wk said:
anyone heard Iocean will recall all of the x7 elite's? i've had a mail today they should do it, but i don't know if it's true or not.
Click to expand...
Click to collapse
I haven't heard about that. Maybe its a fake email. Did it say what the fault was?
Joshafc said:
I think I figured out that the error above means you are trying to flash an incorrect ROM. Make sure you are using the right one and also make sure you're using the latest version of sp flash tool.
Once I downloaded a later version of the flash tool it began installing the ROM but then a different error appeared.
So I formatted the nand with the sp flash tool.
Then I flashed the stock ROM again and it worked
Formatting it seemed to make the errors go away even though its advised not to do so.
Sent from my iOCEAN X7 using xda app-developers app
Click to expand...
Click to collapse
How to format the nand with sp flash tool, I use the latest version?
And can you point me to good original stock ROM?
Thank you!
lolet said:
I fixed this error by completely removing and reinstalling other drivers for mtk vcom loader
Click to expand...
Click to collapse
I tried reinstalling drivers, also tried other drivers, but this doesn't help...
I've had the same problem with the following installation Sp Tools
SP_Flash_Tool_exe_v3.1316.0.150
Rom: MP_mt89_v9_iocean_ousheng_jb2_20130520-184014_zhongyeqing_PC
http://d-h.st/ESX
Iocean X7 Youth
I don't have the same problem but i flashed the latest version of official rom for iOcean x7 Youth : 03 july 2013 : and wtf no more internal sdcard only the rom stockage. So i can't download anything, i can't use camera .
On the official website, I read that before flashing the 20 may 2013 rom one and the 03 July 2013 one, your baseband version have to be 23/04 or higher( you have to flash the 23/04 official rom first). This is only avalaible for the YOUTH version.
So tomorrow i will try what i said below to see if i have internal sd card again.
noob question::: since the iocean x7 young and turbo are the same phones...only different clock rates...will flashing the firmware for turbo on iocean x7 young work??assuming that the mtk6589T and mtk6589 are the same chipset only different clock rates??
Micromax A116 (Cant flash Rom)Brick Problem Solved
tukulll said:
these are common problems when flashing MT65xx based phones,
ie : error 4008, 4xxx, 5xxx whatever those codes mean, no explanation after extensive search on google.
once I managed to flash this one phone successfully, but I don't know exactly what I did.
as long as I recall, I tried to delete the whole flashtool folders, re-extract them, let the phone cool down a bit
and oh, try to press volume up, or down button (varies on devices) while connecting to USB, once the flashing progress bar starts, release the button.
In the flashtool option, at the OPTIONS-->DA DOWNLOAD ALL-->, check WITHOUT BATTERY.
and in the option, DA DOWNLOAD ALL--> SPEED, check DO NOT SWITCH SPEED.
try flashing your phone without battery inserted, it works many times for me.
NOTE : BEWARE, flashing your MTK65xx based phone, sometimes this tool tried to REMOVE YOUR PHONE's IMEI information, so take caution !
I haven't managed how to prevent IMEI removal when flashing those phones, because I'm not a developer.
Hope this helps.
Click to expand...
Click to collapse
Thanks a lot. My Micromax a116 was brick. Now its alive.
Here I am with the same problem in a N920e... AND IT'S NOT MINE! :crying:
I'll have to pay it to the owner if I can't solve this:
DaniPhii said:
Here I am with the same problem in a N920e... AND IT'S NOT MINE! :crying:
I'll have to pay it to the owner if I can't solve this:
View attachment 2243401
Click to expand...
Click to collapse
Clearly: Wrong driver. I had also this error. SPflash tool did not readback. I did not flash anything! I fixed this by showing the nonpresent devices in devicemanagement (google for show nonpresent devices for explanation)
Go to com ports, and delete all mediatek drivers except preloader driver. Now start over. It can help if you choose the same usb port where you had success last time.
SP flash tool shows in the statusbar which driver it is using.
mistraller said:
Clearly: Wrong driver. I had also this error. SPflash tool did not readback. I did not flash anything! I fixed this by showing the nonpresent devices in devicemanagement (google for show nonpresent devices for explanation)
Go to com ports, and delete all mediatek drivers except preloader driver. Now start over. It can help if you choose the same usb port where you had success last time.
Click to expand...
Click to collapse
Yes, you got it
SP Flash Tool couldn't find my phone, but now it works
It's exactly a windoze driver problem.
Going to devicemanagement, in LAN-Devices I a had an Alcatel device,
chosing driver by hand and use the mtk usb driver, now Flashtool finds the phone
Thanks a lotttttttt....
shiv.kbh said:
Thanks a lot. My Micromax a116 was brick. Now its alive.
Click to expand...
Click to collapse
Thanks a lot man i unbricked my bolt a58 with this...thanks thanks...
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
https://mega.nz/#!BKQS2a4K!G5YrKHWUy2HvL2TOqOlLzwn7Sulp7q8i7-h8uVi0uk8
UNIVERSAL V2 - IF TOP DONT WORK
https://mega.nz/#!bphxHJBB!jRhp0AeNa8orSwscFJHJdE7M14_GxQgbHpnbq-21vy8
Step 1 Download & Extract the bundle for your device
You will be getting either a zip or 7z file, personally I would use 7zip to extract these files, you should get a recovery.img and also a folder called TWRP. If you have these two things move on to step 2
Step 2 - Locations
Both SD Card and USB being formatted Fat32 - Some boxes except most s905 you can use the SD card for both TWRP folder and recovery.img, Regardless I use SD only for recovery.img, so drag and drop the recovery.img onto the Fat32 SD Card and Drag and drop the TWRP folder onto the Fat32 USB drive. Done
Step 3 - Formatting before installing.
Connect everything but the power - Connect a real USB mouse/Airmouse to the box due to the regular remote will not work, connect the USB drive and connect the SD Card, Everything but power. Some boxes have a reset button on the side and some the reset button is inside the AV jack, you will feel it, If in the AV jack simply use a toothpick or use a Q Tip with the cotton end removed and slide it in the AV jack and you will feel the button.
HOLD THIS BUTTON AND DO NOT LET GO - At the same time plug it in and keep holding, boxes with physical power button press this now. You will be presented with a blue screen, you will get a read only scren most likely, slide to proceed.
First thing first I always recommend backing up partitions incase something is to go wrong. There are tons of cloned boxes its hard to cover them all. I personally would go to backup. Locate where it says storage, and change from internal to usb otg for USB drive or external sd for your SD Card. Backup all your partitions.
When done, go back. Press the little house button on the screen or the back button until back at the TWRP menu, go to restore, Make sure usb otg or external sd is chosen, wherever you put the TWRP folder, If you are using a box not from me PM me the model and I will confirm what to restore, for example, M8, M8S BCM and AP models, MX3, M10, You can restore all, S912 boxes some are different so PM me to be safe. After I tell you what to restore do so. Let it do its thing. Once done, reboot and enjoy. If it fails by any means. Do not reboot, just go back and choose wipe, format data, type yes press enter. Once done just go back and restore data JUST BY ITSELF so untick everything but data, once finished restore all the other partitions. All done
Enjoy the build - When you first boot my firmware let it sit after it boots for a good minute or two. It will auto load my custom firmware patches and more.
If you are using M8, M8S, M10, MXq you need to follow below -
When you start the TV box. Let it sit a few minutes and first things first. In Android applications click on No Frills CPU - the accelerometer and when it opens click apply and than exit. It is super important with my custom rom to unlock the other 2 CPU Cores and the other 4 GPU Threads. If this does not make sense just go into my apps and look for no frills, same app as on the desktop you will just see the name instead.
NOT EVERY FIRMWARE HAS NO FRILLS - IF NOT DO NOT WORRY ABOUT IT.
i do not own the firmware
credits go to ghostware.
Congrats!
Just a clarification, which ROM are you using as "skeleton", and what ROM did you take the /system partition from?
MyM8SFinallyWorks said:
Just a clarification, which ROM are you using as "skeleton", and what ROM did you take the /system partition from?
Click to expand...
Click to collapse
i used a m8s+ rom and the 5.1.1 rom from acemax the only problem is with the m8s+ rom is ethernet dont work so by doing this i got ethernet to work.
Thanks for this link
Hello, I just want to ask how do you know if your box is the "ap3660" box and how can you find out?
my box is the m8s amlogic s812
thanks.
lutty321 said:
Hello, I just want to ask how do you know if your box is the "ap3660" box and how can you find out?
my box is the m8s amlogic s812
thanks.
Click to expand...
Click to collapse
you have to open it and look inside
Hi. I cannot get my box to the boot menu with the toothpick reset?!? It just loops into rebooting and goes back to original setup. I have disabled the restore from backup too but still? Pls help!!!!
Tazosman said:
Hi. I cannot get my box to the boot menu with the toothpick reset?!? It just loops into rebooting and goes back to original setup. I have disabled the restore from backup too but still? Pls help!!!!
Click to expand...
Click to collapse
if you have the recovery.img file on the root of the sd card, toothpick method should take you to TWRP where you can then flash the zip. did you give it some time (with the reset button pressed in)? it can take approx 10 seconds sometimes.
Failed signiture
Hi guys i have tried to flash my box with the firmware that was posted here by daniel and i am getting the problem of it saying....
"E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted "
Ive tried it a few times and still no luck.
Could anyone point me in the right direction of a successful flash please?
Thanks in advance
Hi
i just tryed this metod but my M8S does not respound anymore(no on light) it seems dat it is deed???Has any body iedea what can i do now?
Hey is there any way to fix the remote volume problem? I restored my remote config from 4.4 but everything worked except the volume button. BTW I have the remote with the red, green, yellow and blue buttons at the volume control.
Devmau53 said:
Hi guys i have tried to flash my box with the firmware that was posted here by daniel and i am getting the problem of it saying....
"E: failed to verify whole-file signiture
E: signiture verification failed
Installation aborted "
Ive tried it a few times and still no luck.
Could anyone point me in the right direction of a successful flash please?
Thanks in advance
Click to expand...
Click to collapse
Either your download is corrupt, or you are not using TWRP to perform the update.
Has anyone been having random freezing and reboots?
wolfpack64 said:
Hey is there any way to fix the remote volume problem? I restored my remote config from 4.4 but everything worked except the volume button. BTW I have the remote with the red, green, yellow and blue buttons at the volume control.
Click to expand...
Click to collapse
I also had that problem even though I flashed the square remote zip after the lollipop update. I might have flashed the M8N remote though to be honest and I don't have the box anymore to test more remote patches.
You can try the M8S remote zip from the link below and report back if it worked for you.
http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s802/eny-acemax-ott/firmware-roms-tools-af/18312-s802-multi-remote-patcher-zips
Hi,
Did install this rom provided by d4nielr on my device M8S CS 812M8 V1.3 20150921
Install was perfect boot once and there was a working 5.1 rom with ethernet
Only if i reboot my device its bricked. red licht only recover whith USB burning tool
This is the 5.1 firmware that reboot correctly but ethernet is not working (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6...aLQuUIGK-c-jbg
Can someone help me with this
highpoiss said:
Hi,
Did install this rom provided by d4nielr on my device M8S CS 812M8 V1.3 20150921
Install was perfect boot once and there was a working 5.1 rom with ethernet
Only if i reboot my device its bricked. red licht only recover whith USB burning tool
This is the 5.1 firmware that reboot correctly but ethernet is not working (M8S(n200c)_to_M8S+ 5.1 20151022-aml_upgrade_package) here https://mega.nz/#!ZUxQSJQK!nt8g1nGV6...aLQuUIGK-c-jbg
Can someone help me with this
Click to expand...
Click to collapse
I had the exact same problem when trying to upgrade to something M8S+ based. Worked perfectly the first time, but I could not start it up after a cold boot. Have you tried my original approach instead using the Team DevDigitel ROM?
MyM8SFinallyWorks said:
I had the exact same problem when trying to upgrade to something M8S+ based. Worked perfectly the first time, but I could not start it up after a cold boot. Have you tried my original approach instead using the Team DevDigitel ROM?
Click to expand...
Click to collapse
Yes did try your approach only the acemax 5.1 firmware wil instal but i have a direct brick at first boot red licht only recover whith USB burning tool
highpoiss said:
Yes did try your approach only the acemax 5.1 firmware wil instal but i have a direct brick at first boot red licht only recover whith USB burning tool
Click to expand...
Click to collapse
And what happens if you first go back to your stock Kitkat 4.4 ROM (with USB burning tool), and then try with my original approach (with SD card)?
MyM8SFinallyWorks said:
And what happens if you first go back to your stock Kitkat 4.4 ROM (with USB burning tool), and then try with my original approach (with SD card)?
Click to expand...
Click to collapse
Same problem installing acemax firmware over original 4.4 rom wil brick my device brick at first boot.
Help needed M8S ap6360 v1.3 20150921
Can someone make a TRWP backup from this rom ? specially the boot file
Also want to know where to download the M8s+ rom what daniel uses in this treat
Thanks
Hi d4nielr,
Wanted to thank you for the excellent work in compiling this ROM to support m8s app6330.
After trying out various ROMs and in the process bricking my device several times and un-bricking it using the burning tool, I finally came across your forum.
Thanks for the wonderful rom and the installation was a breeze and smooth sailing throughout.
Btw, for the installation I can only use the other most USB port. If I insert the sd card into the inner most usb port, it will take me to the bootloader.
So, for the TEAMWIN logo to appears, I need to put the sd card into the outer most usb port which is located at the back of my m8s unit.
cheers.......
Update.....
Unfortunately, after a cold boot, it doesn't work any longer. Back to kitkat using usb burning tool.
RCA 10" Touchscreen Tablet PC/DVD Combo Featuring Android 6.0 (Marshmallow)
*No idea why it says PC/DVD as its Android not Windows.
ASIN/Model numbers: ASIN: B077L4VBHK Model: DRP2091
RCA typical RCT number: RCT6603W47M7
Chipset/CPU: MT8127
Ports: 1x Mirco USB (supports ADB! etc. unlike VikingPRO), 1xUSB A, 1xHDMI (mini i believe), 1xMicroSD slot (supports up to 128GB)
Special: 1xDVD/CD Reader/Drive. has unlockable bootloader via fastboot oem unlock
Root Attempts: (Failed: KingoRoot, SRS, KingRoot, RootMaster)
MTK Droid Root & Tools and SP Flash Tools don't seem to work right with this cant create scatter etc. (i assume because of MT8127)
Links:
Walmart/Wally World
Amazon
if any dev could help me root this and get custom recovery would be great.
UPDATE: Thanks to NepoRood (and my testing) theres now CWM recovery (attached to post extract zip and flash img via fastboot flash recovery command.) unfortunately we were still unable to get root access.. if anyone has this device or wants to help root this pm me.
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
NepoRood said:
I found various firmware downloads, but need to know the exact type of firmware you are running.
Example of one I found: rct6603w47m7-android6.0-v23-v2.15.80 (<-- underlined part is what matters)
If you boot into recovery, it should show you the type of firmware you have.
Click to expand...
Click to collapse
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
darkensx said:
DRP2091-android6.0-v62-v1.19.90-E02
*also says on very bottom of screen "supported API: 3"
**DRP2091 is rct6603w47m7 not sure why there's so many different model/serial numbers referencing the same exact device...
also i managed to dump the whole device via SP tools readback on linux so if anything beyond recovery or boot img are needed i should have it.
Click to expand...
Click to collapse
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
NepoRood said:
That version isn't on the site (or any v1.19.x), I'll download the images from the OP in a bit and see what's inside...
Click to expand...
Click to collapse
Had the same issue also I came across a bunch of ota test files on a Chinese site but links were dead and because no ota update is available i can't grab the ota url or file name. So ended up hitting a dead end.
Would it be possible to bypass the activation code screen with cwm or twrp? Or maybe put a different version of android on the tablet, other than marshmallow.?
darkensx said:
Additional files attached maybe someone can build me cwm or twrp for this as i could never get anything to build for mtk devices.
Click to expand...
Click to collapse
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
I have no idea
johnnymack said:
I'm having same problem could someone help me root this tablet explain as easy as possible and slow and clear directions
Click to expand...
Click to collapse
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
BP9375 said:
I've got the RCT6603W47M7 tablet, but here in the UK it goes by the name of RCA Neptune 10.1L.
Problem is I have bricked it and I am now trying to recover it using SP Flash Tools. I have tried 2 different stock ROMs, only to have nothing but errors and interruptions during flashing. (errors 2004 and 4008). My tablet is fully charged yet it will randomly disconnect during flashing. I've tried both the MTKAllInOne.bin and DA_SWSEC.bin but I still get the same problem either way.
I've tried different USB ports, different cables and the two download agents that I just mentioned but I am stumped.
I wanted to try the ROM found here https://www.needrom.com/download/rca-rct6603w47m7/
But as I don't have a premium account I cannot access it.
Any ideas? This is very frustrating.
Click to expand...
Click to collapse
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
darkensx said:
problem with the cwm recovery if i remember correctly is any thing flashed by it doesnt take the device will just bootloop
i no longer have the device currently i might pickup another at some point... i cant remember if i used the micro usb port to flash or if i had to use a usb male to male cable..
Click to expand...
Click to collapse
Thank you for your reply, I was worried that this discussion was dead. That's frustrating to say the least! Damn! Well, I don't know if this will work but I found another device that is also a MT8127 and has exactly the same spec of this tablet. My point being is that I found a TWRP image for that device, and because it's the same chip set I assume that it'll work for this device too?
If I can get my bricked tablet to even turn on I shall try it. It also makes me wonder that if we were able to root the device, would we be able to access the internal storage by normal means? By using the micro USB ? Either way it'd be great to have it rooted.
I stayed up all night last night trying to flash this tablet and still no luck, it keeps disconnecting half way through.
this phone use mt6739.so i want to flash it the twrp to my phone.i dunno to unlock the bootloader but the twrp file not have for this device.
I just saw this post as I too have a Honor 7S
There is NO TWRP for our device.
The TWRP for the Honor 7A/7C/7X and Honor 7 doesn't work on our device and you got to pay 4 euros to unlock the bootloader before you can even flash TWRP (and there isn't one)
This Device is treble compatible but now I've found out there is zero development and no Devs Interested in it it's a complete and utter waste of time and has gone back into its box, never to be seen again.
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Samuel Ladziansky said:
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Click to expand...
Click to collapse
Hi I have a problem. I'm having brom issues in trying to flash it
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
usab1oy said:
Hi I have a problem. I'm having brom issues in trying to flash it
Click to expand...
Click to collapse
and little hint
dont flash whole rom if the phone can boot becasue after clean flash "format+download"
you lost log and cust partition because the image files are not secureboot signed and your phone get in to bootloop
and also you lost imei codes so no cellular after that
If you do so
you can fix it in that recovery were I enabled option to format log partition
after you format log to ext4, your phone will boot but without huawei/honor bootanimation
you dont need to worry about cust partition, if you didnt format it it still boot but without bootanimation and you lost some of garbage apps that are in that partition (amazon etc...)
(twrp boots in russian language, idk for now how to change it to boot in english or slovak lanuage (because Im from slovakia) and also it have Lenovo Logo becasuse I use sources from Lenovo A5 that have same cpu)
I will make in future separated thread for this....
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Samuel Ladziansky said:
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
Click to expand...
Click to collapse
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
usab1oy said:
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
Click to expand...
Click to collapse
you can patch it or flash it without disconecting the battery
Here is how:
turn it off
Push and hold volume down
While holding volume down connect usb cable
But is recomended to disconect battery because the phone can boot up instead to go in flash mode.
usab1oy said:
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Click to expand...
Click to collapse
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Samuel Ladziansky said:
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Click to expand...
Click to collapse
Yeah. For the flash mode, I wonder why his own he said I need to hold the volume up and down button at the same time. But thanks I'll do it and let you know.
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Samuel Ladziansky said:
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Click to expand...
Click to collapse
At this point. Might just abandon it. Thanks for everything. Ran into laptop issue on my third trial lol.
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Samuel Ladziansky said:
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Click to expand...
Click to collapse
Honestly. I spend a whole night researching videos for the phone. Only to get that link I send. And after all that. It still didn't work. Lol. I have a Poco x3 pro. I wonder if snapdragon android 12 can be rooted. Probably going to try it next month or so.
Snapdragon is eazy for root.
I have Redmi note 11 and it was easy, now I running on Android 13 from stock android 11, if you will need some help with something, I'm here, and I think there is device forum so there is community for that device